gamearchive-cli
The package installs a Node.js CLI tool from the official npm registry under a scoped project owned by the same developer; the install target is a declared dependency from the project's own ecosystem, not an undeclared external package, making this a normal and low-risk AUR packaging pattern.
Triggered rules
llm_review
The static rules flagged this MEDIUM, but an AI model (qwen/qwen3-235b-a22b-07-25) reviewed the full PKGBUILD and judged it LOW (confidence 90%): The package installs a Node.js CLI tool from the official npm registry under a scoped project owned by the same developer; the install target is a declared dependency from the project's own ecosystem, not an undeclared external package, making this a normal and low-risk AUR packaging pattern.
1 higher static finding superseded - not the current verdict (shown for transparency)
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"
PKGBUILD
1 offending line(s) highlighted_npmname_base=gamearchive
_npmname=${_npmname_base}-cli
_npmscope=@camoto
pkgname=${_npmname} # All lowercase
pkgver=latest
pkgrel=1
pkgdesc="Read and write archive files used by DOS games"
arch=(any)
url="http://github.com/Malvineous/${_npmname_base}js"
license=()
depends=('nodejs' )
makedepends=('npm')
optdepends=()
pkgver() {
# Grab the latest version from npmjs.org
#npm view "${_npmscope}/${_npmname}@latest" version
# ...but as a dodgy hack use the version of the parent package instead. This
# way when the base library gets updated this package version number will
# change to match, even though technically the package we're installing
# hasn't been updated, only one of its dependencies has.
npm view "${_npmscope}/${_npmname_base}@latest" version
}
package() {
#npm install -g --user root --prefix "${pkgdir}/usr" "${_npmscope}/${_npmname}@${pkgver}"
# We should be installing ${pkgver} but since that is now the parent library
# version, it won't match the -cli package version. So we just use 'latest'
# to get whatever CLI version is there. It will always install the latest
# version of the underlying library because of the '*' spec in package.json
# so it should always match the $pkgver.
npm install -g --user root --prefer-online --prefix "${pkgdir}/usr" "${_npmscope}/${_npmname}@latest"
# Non-deterministic race in npm gives 777 permissions to random directories.
# See https://github.com/npm/cli/issues/1103 for details.
find "${pkgdir}/usr" -type d -exec chmod 755 {} +
# npm gives ownership of ALL FILES to build user
# https://bugs.archlinux.org/task/63396
chown -R root:root "${pkgdir}"
# Remove references to srcdir/pkgdir
find "$pkgdir" -name package.json -print0 | xargs -r -0 sed -i '/_where/d'
}
Scan history
| Scanned at (UTC) | Severity | Rules |
|---|---|---|
| 2026-11-01 00:21:48 | Low | 2 |
| 2026-10-31 00:07:41 | Low | 2 |
| 2026-10-30 00:29:30 | Low | 2 |
| 2026-10-29 00:13:55 | Low | 2 |
| 2026-10-28 00:06:54 | Low | 2 |
| 2026-10-27 00:23:28 | Low | 2 |
| 2026-10-26 00:12:40 | Low | 2 |
| 2026-10-25 00:20:48 | Low | 2 |
| 2026-10-24 00:14:55 | Low | 2 |
| 2026-10-23 00:02:19 | Low | 2 |
| 2026-10-22 00:13:10 | Low | 2 |
| 2026-10-21 00:12:50 | Low | 2 |
| 2026-10-20 00:10:31 | Low | 2 |
| 2026-10-19 00:03:55 | Low | 2 |
| 2026-10-18 00:06:55 | Low | 2 |
| 2026-10-17 00:21:55 | Low | 2 |
| 2026-10-16 00:12:47 | Low | 2 |
| 2026-10-15 00:28:05 | Low | 2 |
| 2026-10-14 00:06:47 | Low | 2 |
| 2026-10-13 00:23:45 | Low | 2 |