aliyunpan-cli-bin

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

MEDIUM

Why flagged The PKGBUILD runs `pip install -r requirements.txt` and `pip install pyinstaller` during the prepare() phase, pulling Python packages from PyPI without pinned versions or checksums. This is a genuine supply-chain concern: any of those PyPI packages could be compromised or typosquatted, and the installed code gets compiled into a standalone binary via PyInstaller and then installed to /usr/bin. Additionally, the dlnap dependency is pulled from a GitHub master branch tarball with SKIP checksum, meaning it is not integrity-verified. The combination of unverified external code execution during build and bundling into a shipped binary represents a real (if not clearly malicious) supply-chain risk. The source tarball itself comes from the official GitHub releases page, which is fine, but the pip-based dependency resolution without lockfile/hashes undermines reproducibility and security.

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:25 pip install -r requirements.txt
PKGBUILD:26 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 75%): The PKGBUILD runs `pip install -r requirements.txt` and `pip install pyinstaller` during the prepare() phase, pulling Python packages from PyPI without pinned versions or checksums. This is a genuine supply-chain concern: any of those PyPI packages could be compromised or typosquatted, and the installed code gets compiled into a standalone binary via PyInstaller and then installed to /usr/bin. Additionally, the dlnap dependency is pulled from a GitHub master branch tarball with SKIP checksum, meaning it is not integrity-verified. The combination of unverified external code execution during build and bundling into a shipped binary represents a real (if not clearly malicious) supply-chain risk. The source tarball itself comes from the official GitHub releases page, which is fine, but the pip-based dependency resolution without lockfile/hashes undermines reproducibility and security.

PKGBUILD

2 offending line(s) highlighted

      1# Maintainer: Atom Long <atom.long@hotmail.com>
    
      2
    
      3_pkgname=aliyunpan
    
      4pkgname=${_pkgname}-cli-bin
    
      5pkgver=3.0.9
    
      6pkgrel=1
    
      7pkgdesc="Aliyunpan CLI"
    
      8arch=('any')
    
      9url="https://github.com/wxy1343/aliyunpan"
    
      10license=("GPL-3.0")
    
      11makedepends=('python-pip')
    
      12provides=("aliyunpan" "aliyunpan-cli")
    
      13conflicts=("aliyunpan" "aliyunpan-cli")
    
      14source=(${_pkgname}-${pkgver}.tar.gz::"${url}/archive/refs/tags/v${pkgver}.tar.gz"
    
      15        dlnap-master.tar::"https://github.com/cherezov/dlnap/archive/master.tar.gz"
    
      16        "0001-upgrade-requirements.patch")
    
      17sha256sums=('bcf6aefbf2990dd1f81a24b9307363b2198d5540b22c6099d4a56ff25010cba4'
    
      18            'SKIP'
    
      19            '130eae5955b74cdc9984c1bc69982480d0b38fdbe719de068a7a12dcc4c8b3d3')
    
      20
    
      21prepare() {
    
      22  cd "${_pkgname}-${pkgver}"
    
      23  mv -vTf "${srcdir}"/dlnap-master dlnap
    
      24  patch -Np1 -i "${srcdir}/0001-upgrade-requirements.patch"
    
      25  pip install -r requirements.txt
    
      26  pip install pyinstaller
    
      27  export PATH=${HOME}/.local/bin:${PATH}
    
      28}
    
      29
    
      30build() {
    
      31  cd ${_pkgname}-${pkgver}
    
      32  pyinstaller -F aliyunpan/main.py -n aliyunpan-cli
    
      33}
    
      34
    
      35package() {
    
      36  cd ${_pkgname}-${pkgver}
    
      37  install -Dm755 ./dist/aliyunpan-cli "$pkgdir/usr/bin/aliyunpan-cli"
    
      38  ln -vsf aliyunpan-cli $pkgdir/usr/bin/aliyunpan
    
      39}
    
      40
    
      41# vim: set et ts=2 sw=2:
    
      42

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