gamemusic-cli

MEDIUM

maintainer Malvineous 0 votes scanned 2026-09-17 00:27:14.276658

View on AUR

Why flagged

The PKGBUILD installs an npm package directly from the npmjs registry at build/install time using `@latest`, with no pinned version, no checksum, and no declared source array. The pkgver() function uses the parent library's version as a proxy (explicitly acknowledged as a 'dodgy hack'), meaning the installed CLI package version is entirely decoupled from the reported pkgver. The actual install always fetches whatever `@latest` resolves to at install time, making this non-reproducible and unverifiable. While the npm scope (@camoto) and package name appear to correspond to a legitimate upstream author (Malvineous on GitHub), the pattern of fetching and executing arbitrary remote code without any integrity check is a genuine supply-chain concern: a compromised npm account or a typosquat could silently deliver malicious code. This is a real medium-severity supply-chain risk, not a false positive.

Triggered rules

Medium npm/yarn/pnpm install of an undeclared external package npm_install_external

Runs `npm/yarn/pnpm install <package>` for a package not in source=(), pulling unpinned, unreviewed code at build time. Severity downgraded: the package declares/looks like a Node.js consumer, where build-time installs are expected.

PKGBUILD:32 npm install -g --user root --prefer-online --prefix "${pkgdir}/usr" "${_npmscope}/${_npmname}@latest"

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 installs an npm package directly from the npmjs registry at build/install time using `@latest`, with no pinned version, no checksum, and no declared source array. The pkgver() function uses the parent library's version as a proxy (explicitly acknowledged as a 'dodgy hack'), meaning the installed CLI package version is entirely decoupled from the reported pkgver. The actual install always fetches whatever `@latest` resolves to at install time, making this non-reproducible and unverifiable. While the npm scope (@camoto) and package name appear to correspond to a legitimate upstream author (Malvineous on GitHub), the pattern of fetching and executing arbitrary remote code without any integrity check is a genuine supply-chain concern: a compromised npm account or a typosquat could silently deliver malicious code. This is a real medium-severity supply-chain risk, not a false positive.

PKGBUILD

1 offending line(s) highlighted

      1_npmname_base=gamemusic
    
      2_npmname=${_npmname_base}-cli
    
      3_npmscope=@camoto
    
      4pkgname=${_npmname} # All lowercase
    
      5pkgver=latest
    
      6pkgrel=1
    
      7pkgdesc="Import, export and convert music files used by DOS games"
    
      8arch=(any)
    
      9url="http://github.com/Malvineous/${_npmname_base}js"
    
      10license=()
    
      11depends=('nodejs' )
    
      12makedepends=('npm')
    
      13optdepends=()
    
      14
    
      15pkgver() {
    
      16	# Grab the latest version from npmjs.org
    
      17	#npm view "${_npmscope}/${_npmname}@latest" version
    
      18	# ...but as a dodgy hack use the version of the parent package instead.  This
    
      19	# way when the base library gets updated this package version number will
    
      20	# change to match, even though technically the package we're installing
    
      21	# hasn't been updated, only one of its dependencies has.
    
      22	npm view "${_npmscope}/${_npmname_base}@latest" version
    
      23}
    
      24
    
      25package() {
    
      26	#npm install -g --user root --prefix "${pkgdir}/usr" "${_npmscope}/${_npmname}@${pkgver}"
    
      27	# We should be installing ${pkgver} but since that is now the parent library
    
      28	# version, it won't match the -cli package version.  So we just use 'latest'
    
      29	# to get whatever CLI version is there.  It will always install the latest
    
      30	# version of the underlying library because of the '*' spec in package.json
    
      31	# so it should always match the $pkgver.
    
      32	npm install -g --user root --prefer-online --prefix "${pkgdir}/usr" "${_npmscope}/${_npmname}@latest"
    
      33
    
      34	# Non-deterministic race in npm gives 777 permissions to random directories.
    
      35	# See https://github.com/npm/cli/issues/1103 for details.
    
      36	find "${pkgdir}/usr" -type d -exec chmod 755 {} +
    
      37
    
      38	# npm gives ownership of ALL FILES to build user
    
      39	# https://bugs.archlinux.org/task/63396
    
      40	chown -R root:root "${pkgdir}"
    
      41
    
      42	# Remove references to srcdir/pkgdir
    
      43	find "$pkgdir" -name package.json -print0 | xargs -r -0 sed -i '/_where/d'
    
      44}
    
      45

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