gamecode-cli
The package installs a Node.js CLI tool from the official npm registry using a scoped package; while the version is not pinned and a dependency is installed without explicit declaration, it is part of the normal npm workflow and targets a legitimate, project-related package from a trusted ecosystem.
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 95%): The package installs a Node.js CLI tool from the official npm registry using a scoped package; while the version is not pinned and a dependency is installed without explicit declaration, it is part of the normal npm workflow and targets a legitimate, project-related package from a trusted ecosystem.
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=gamecode
_npmname=${_npmname_base}-cli
_npmscope=@camoto
pkgname=${_npmname} # All lowercase
pkgver=latest
pkgrel=1
pkgdesc="Modify text strings in executable files used by MS-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-09-17 00:27:14 | Low | 2 |
| 2026-09-16 00:03:17 | Low | 2 |
| 2026-09-15 00:25:31 | Low | 2 |
| 2026-09-14 00:27:57 | Low | 2 |
| 2026-09-13 00:19:54 | Low | 2 |
| 2026-09-12 00:25:17 | Low | 2 |
| 2026-09-11 00:19:22 | Low | 2 |
| 2026-09-10 00:22:44 | Low | 2 |
| 2026-09-09 00:04:09 | Low | 2 |
| 2026-09-08 00:18:08 | Low | 2 |
| 2026-09-07 00:30:15 | Low | 2 |
| 2026-09-06 00:17:06 | Low | 2 |
| 2026-09-05 00:16:27 | Low | 2 |
| 2026-09-04 00:03:13 | Low | 2 |
| 2026-09-03 00:15:47 | Low | 2 |
| 2026-09-02 00:02:31 | Low | 2 |
| 2026-09-01 00:11:19 | Low | 2 |
| 2026-08-31 00:19:57 | Low | 2 |
| 2026-08-30 00:04:14 | Low | 2 |
| 2026-08-29 00:29:17 | Low | 2 |