btcli

maintainer Connor · 0 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged The PKGBUILD downloads a prebuilt binary (btcli) from concise.cc, a personal domain belonging to the maintainer, not from the official upstream GitLab repository (gitlab.com/a4to/btcli). While a PGP signature is present and validated (validpgpkeys), the binary artifact is self-hosted by the maintainer on their own infrastructure rather than being built from source or fetched from the official project's release infrastructure. This is a genuine supply-chain concern: if concise.cc is compromised or the maintainer silently swaps the artifact, users receive an arbitrary binary executed with install -Dm755. The arch=(any) designation is also suspicious for a compiled binary. The sha512sums provide some integrity protection but do not protect against the maintainer intentionally substituting a malicious binary. This pattern — prebuilt binary from a personal/unofficial host — is the canonical medium-risk supply-chain scenario.

Triggered rules

MEDIUM source=() URL on a non-standard host 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:12 "https://concise.cc/pkg/${pkgname}-${pkgver}-${pkgrel}-$arch.pkg.tar.zst"

MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 82%): The PKGBUILD downloads a prebuilt binary (btcli) from concise.cc, a personal domain belonging to the maintainer, not from the official upstream GitLab repository (gitlab.com/a4to/btcli). While a PGP signature is present and validated (validpgpkeys), the binary artifact is self-hosted by the maintainer on their own infrastructure rather than being built from source or fetched from the official project's release infrastructure. This is a genuine supply-chain concern: if concise.cc is compromised or the maintainer silently swaps the artifact, users receive an arbitrary binary executed with install -Dm755. The arch=(any) designation is also suspicious for a compiled binary. The sha512sums provide some integrity protection but do not protect against the maintainer intentionally substituting a malicious binary. This pattern — prebuilt binary from a personal/unofficial host — is the canonical medium-risk supply-chain scenario.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Connor Etherington <connor@concise.cc>
    
      2# ---
    
      3pkgname=btcli
    
      4pkgver=0.1.0
    
      5pkgrel=1
    
      6pkgdesc="A simple, easy to use, CLI bluetooth connections manager"
    
      7arch=(any)
    
      8url="https://gitlab.com/a4to/${pkgname}"
    
      9license=('MIT')
    
      10depends=()
    
      11source=(
    
      12  "https://concise.cc/pkg/${pkgname}-${pkgver}-${pkgrel}-$arch.pkg.tar.zst"
    
      13  "https://concise.cc/pkg/${pkgname}-${pkgver}-${pkgrel}-$arch.pkg.tar.zst.sig"
    
      14  )
    
      15sha512sums=(
    
      16  '61142e74ccd70ef40f25a4064235504ee32ed461b5f702c1d9d6159623f0b2f0b58d5146ad56c45a35c8e2a3b521b1054041a844c093103011ddb4e55f3fcfc4'
    
      17  'eeb5edbbabccd266ebbfb06656bc4d2bd983eb6b9c821b66f55d3cb6e94bcc022e0069b8f9c8fa38fa925c94b618ff71d1945349e2cac332d35f09fac3bcbe69'
    
      18  )
    
      19md5sums=(
    
      20  'da0f1e2749c1a4e9b143fcf3ba0e6ed1'
    
      21  '3f538d3a7747690c5906347a9b56acf7'
    
      22  )
    
      23validpgpkeys=('9A1F3F41DDA55A60331CB8DD3714CB0967D15980')
    
      24
    
      25package() {
    
      26    install -Dm644 usr/share/licenses/${pkgname}/LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
    
      27    install -Dm755 usr/bin/${pkgname} "${pkgdir}/usr/bin/${pkgname}"
    
      28}
    
      29

Scan history

Scanned at (UTC)	Severity	Rules
2026-08-03 00:08:14	MEDIUM	2
2026-08-02 00:16:08	MEDIUM	2
2026-08-01 00:11:18	MEDIUM	2
2026-07-31 00:14:10	MEDIUM	2
2026-07-30 00:17:23	MEDIUM	2
2026-07-29 00:25:53	MEDIUM	2
2026-07-28 00:07:28	MEDIUM	2
2026-07-27 00:24:32	MEDIUM	2
2026-07-26 00:07:32	MEDIUM	2
2026-07-25 00:13:44	MEDIUM	2
2026-07-24 00:02:28	MEDIUM	2
2026-07-23 00:14:47	MEDIUM	2
2026-07-22 00:29:32	MEDIUM	2
2026-07-21 00:24:15	MEDIUM	2
2026-07-20 00:19:49	MEDIUM	2
2026-07-19 00:17:08	MEDIUM	2
2026-07-18 00:14:48	MEDIUM	2
2026-07-17 00:06:16	MEDIUM	2
2026-07-16 00:05:41	MEDIUM	2
2026-07-15 00:09:25	MEDIUM	2