meshcmd-bin
The PKGBUILD downloads a prebuilt x86_64 binary from alt.meshcentral.com (a subdomain of meshcentral.com, which is the official MeshCentral/MeshCommander project domain operated by Intel/AMT team). The URL uses a query-parameter dispatch (?meshcmd=6) rather than a versioned release path, which means the downloaded binary is not pinned to a specific release artifact by URL — however, the b2sum provides integrity verification. The host is a subdomain of the official project domain (meshcentral.com), not a random personal host, so the supply-chain risk is lower than a truly unofficial mirror. Nevertheless, the binary is executed directly, there is no source build, and the download URL is dynamic/non-versioned (the same URL could serve a different binary if the server changes what '6' maps to, though the checksum would catch substitution). The real concern is that this is a prebuilt binary installed to /usr/bin with no source compilation, from a non-GitHub-releases URL, which is a legitimate medium supply-chain concern even with a checksum. The checksum mitigates active interception but not a compromised upstream server that updates the binary and the PKGBUILD simultaneously. Overall: genuine medium risk (prebuilt binary from a non-standard release URL), but not high since the domain is the official project domain and a strong checksum is present.
Triggered rules
source_untrusted_domain
One or more source=() URLs point to a host outside the trusted allowlist (github.com, gitlab.com, codeberg.org, pypi.org, …).
-
PKGBUILD:13
source=("meshcmd::https://alt.meshcentral.com/meshagents?meshcmd=6")
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD downloads a prebuilt x86_64 binary from alt.meshcentral.com (a subdomain of meshcentral.com, which is the official MeshCentral/MeshCommander project domain operated by Intel/AMT team). The URL uses a query-parameter dispatch (?meshcmd=6) rather than a versioned release path, which means the downloaded binary is not pinned to a specific release artifact by URL — however, the b2sum provides integrity verification. The host is a subdomain of the official project domain (meshcentral.com), not a random personal host, so the supply-chain risk is lower than a truly unofficial mirror. Nevertheless, the binary is executed directly, there is no source build, and the download URL is dynamic/non-versioned (the same URL could serve a different binary if the server changes what '6' maps to, though the checksum would catch substitution). The real concern is that this is a prebuilt binary installed to /usr/bin with no source compilation, from a non-GitHub-releases URL, which is a legitimate medium supply-chain concern even with a checksum. The checksum mitigates active interception but not a compromised upstream server that updates the binary and the PKGBUILD simultaneously. Overall: genuine medium risk (prebuilt binary from a non-standard release URL), but not high since the domain is the official project domain and a strong checksum is present.
PKGBUILD
1 offending line(s) highlighted# Maintainer: Matteo Piccinini (loacker) <matteo.piccinini@gmail.com>
pkgname=meshcmd-bin
pkgver=1.1.46
pkgrel=1
pkgdesc="A command line tool for performing many Intel AMT management operations"
arch=("x86_64")
url="https://www.meshcommander.com/meshcommander/meshcmd"
license=("Apache-2.0")
depends=(
'glibc'
)
source=("meshcmd::https://alt.meshcentral.com/meshagents?meshcmd=6")
b2sums=('7b3ccabb29faa6e8204494f33c8f30f4251299791bc8382b2186a9c382c4956464d2eb8a5fe31b48d3cfade82d6621f803e1aa8481bcdae821cb59bcf5e737b3')
package() {
install -Dm755 "meshcmd" "${pkgdir}/usr/bin/meshcmd"
}
Scan history
| Scanned at (UTC) | Severity | Rules |
|---|---|---|
| 2026-09-17 00:27:14 | Medium | 2 |
| 2026-09-16 00:03:17 | Medium | 2 |
| 2026-09-15 00:25:31 | Medium | 2 |
| 2026-09-14 00:27:57 | Medium | 2 |
| 2026-09-13 00:19:54 | Medium | 2 |
| 2026-09-12 00:25:17 | Medium | 2 |
| 2026-09-11 00:19:22 | Medium | 2 |
| 2026-09-10 00:22:44 | Medium | 2 |
| 2026-09-09 00:04:09 | Medium | 2 |
| 2026-09-08 00:18:08 | Medium | 2 |
| 2026-09-07 00:30:15 | Medium | 2 |
| 2026-09-06 00:17:06 | Medium | 2 |
| 2026-09-05 00:16:27 | Medium | 2 |
| 2026-09-04 00:03:13 | Medium | 2 |
| 2026-09-03 00:15:47 | Medium | 2 |
| 2026-09-02 00:02:31 | Medium | 2 |
| 2026-09-01 00:11:19 | Medium | 2 |
| 2026-08-31 00:19:57 | Medium | 2 |
| 2026-08-30 00:04:14 | Medium | 2 |
| 2026-08-29 00:29:17 | Medium | 2 |