lbry-sdk

MEDIUM

maintainer orphaned 0 votes scanned 2026-11-01 00:21:48.120785

View on AUR

Why flagged

The PKGBUILD uses `pip install pyinstaller` during the build phase without pinning a version or providing a checksum, pulling an arbitrary version of pyinstaller from PyPI at build time. While PyPI is a legitimate ecosystem mirror, installing an unpinned external package during build is a real supply-chain concern: a compromised or typosquatted pyinstaller release could execute arbitrary code during the build, and the resulting binary (a PyInstaller-bundled single-file executable) is then installed directly to /usr/bin/lbrynet. The risk is compounded by the use of `|| true` on patches (masking patch failures silently) and the fact that the final installed artifact is a compiled binary whose contents depend on the unverified pip-fetched tool. This is a genuine medium-severity supply-chain concern, not a false positive.

Triggered rules

Medium pip install of an external package pip_install_external

`pip install <package>` fetches an unpinned package from PyPI at build time, outside source=() and makepkg's checksums.

PKGBUILD:33 pip install pyinstaller

Medium AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD uses `pip install pyinstaller` during the build phase without pinning a version or providing a checksum, pulling an arbitrary version of pyinstaller from PyPI at build time. While PyPI is a legitimate ecosystem mirror, installing an unpinned external package during build is a real supply-chain concern: a compromised or typosquatted pyinstaller release could execute arbitrary code during the build, and the resulting binary (a PyInstaller-bundled single-file executable) is then installed directly to /usr/bin/lbrynet. The risk is compounded by the use of `|| true` on patches (masking patch failures silently) and the fact that the final installed artifact is a compiled binary whose contents depend on the unverified pip-fetched tool. This is a genuine medium-severity supply-chain concern, not a false positive.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: missing <liri_bucketful at slmail dot me>
    
      2pkgname=lbry-sdk
    
      3pkgver=0.112.0
    
      4pkgrel=1
    
      5pkgdesc="The LBRY SDK for building decentralized, censorship resistant, monetized, digital content apps."
    
      6arch=('x86_64')
    
      7url="https://github.com/lbryio/lbry-sdk"
    
      8license=('MIT')
    
      9makedepends=('git' 'cmake' 'python')
    
      10provides=('lbrynet')
    
      11conflicts=('lbrynet')
    
      12options=('!buildflags')
    
      13source=("${pkgname}-${pkgver}.tar.gz::https://github.com/lbryio/lbry-sdk/archive/refs/tags/v${pkgver}.tar.gz"
    
      14        "lbry-sdk-${pkgver}.patch"
    
      15        'lbry-venv.patch')
    
      16sha256sums=('bc1466b1ef99ffacbb7ee1ef5df301a6c9ce86c2df505de714ba5db69839c2ce'
    
      17            '6d7ae523b05dab708f7bcb6fe0ea6d0008512cc1d895202204dfacfccb27d83d'
    
      18            '053e7f128eb0ab4e5637f94a3a08af3a80c851b57f4eab26710ec1c85bcce6e7')
    
      19
    
      20build() {
    
      21	python -m venv lbry-venv
    
      22	source lbry-venv/bin/activate
    
      23
    
      24	patch --strip=0 --input="lbry-sdk-${pkgver}.patch" || true
    
      25	cd "lbry-sdk-${pkgver}"
    
      26	make install
    
      27
    
      28	cd ..
    
      29	patch --strip=0 --input=lbry-venv.patch || true
    
      30
    
      31	mkdir build
    
      32	cd build
    
      33	pip install pyinstaller
    
      34	pyinstaller --onefile --name lbrynet "../lbry-sdk-${pkgver}/lbry/extras/cli.py"
    
      35}
    
      36
    
      37package() {
    
      38	install -Dm755 "${srcdir}/build/dist/lbrynet" "${pkgdir}/usr/bin/lbrynet"
    
      39	install -Dm644 "${srcdir}/lbry-sdk-${pkgver}/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
    
      40}
    
      41

Scan history

Scanned at (UTC)	Severity	Rules
2026-11-01 00:21:48	Medium	2
2026-10-31 00:07:41	Medium	2
2026-10-30 00:29:30	Medium	2
2026-10-29 00:13:55	Medium	2
2026-10-28 00:06:54	Medium	2
2026-10-27 00:23:28	Medium	2
2026-10-26 00:12:40	Medium	2
2026-10-25 00:20:48	Medium	2
2026-10-24 00:14:55	Medium	2
2026-10-23 00:02:19	Medium	2
2026-10-22 00:13:10	Medium	2
2026-10-21 00:12:50	Medium	2
2026-10-20 00:10:31	Medium	2
2026-10-19 00:03:55	Medium	2
2026-10-18 00:06:55	Medium	2
2026-10-17 00:21:55	Medium	2
2026-10-16 00:12:47	Medium	2
2026-10-15 00:28:05	Medium	2
2026-10-14 00:06:47	Medium	2
2026-10-13 00:23:45	Medium	2