registry / @nemoobc/opencode-termux / 1.20.16
@nemoobc/opencode-termux@1.20.16
opencode CLI native untuk Termux/Android tanpa proot — membundel binary opencode resmi (upstream opencode 2.2.0) + patch ELF biar jalan native
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found an Android-oriented bundle installer and a launcher for the bundled CLI. Its configuration setup preserves existing files, and no concrete attack behavior was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The package postinstall hook runs, or the user invokes the launcher.
Impact
The inspected behavior is consistent with the package's Termux CLI purpose; existing OpenCode configuration files are left in place.
Mechanism
The installer fetches runtime and CLI archives for the bundle; the launcher invokes the bundled CLI and exposes explicit update and diagnostic commands.
AI rationale
Source inspection found an Android-oriented bundle installer and a launcher for the bundled CLI. Its configuration setup preserves existing files, and no concrete attack behavior was identified.
Evidence
package.jsonbin/opencode-termux.jsinstall.mjs
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs the installer; it skips setup outside Android unless explicitly forced.
- The installer downloads the upstream OpenCode bundle and Alpine runtime components to assemble the Termux bundle.
- The installer adds default OpenCode configuration only when the user has no existing file.
- The launcher dispatches update, diagnostic, and version commands explicitly, then runs the bundled CLI for other arguments.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node install.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/opencode-termux.jsView file
•Manifest-reachable source resolves another installed package, overwrites its runtime code, and injects package-defined remote behavior.
bin/opencode-termux.js:
const res = await fetch(`https://registry.npmjs.org/${reg}/latest`)
if (!fs.existsSync(rc)) fs.writeFileSync(rc, "nameserver 1.1.1.1\nnameserver 8.8.8.8\n")
if (!fs.existsSync(hh)) fs.writeFileSync(hh, "127.0.0.1 localhost\n")
fs.writeFileSync(path.join(root, "package.json"), JSON.stringify(PKG, null, 2) + "\n")
const r = spawnSync(process.execPath, ["-e", "fetch('https://registry.npmjs.org/-/ping').then(r=>{if(!r.ok)process.exit(1)})"], {
Findings
4 High5 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighEntrypoint Foreign Package Code Overwritebin/opencode-termux.js
HighSandbox Evasion Gated Capabilitybin/opencode-termux.js
HighPrevious Version Dangerous Deltabin/opencode-termux.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binaryprebuilt/ld-musl-aarch64-termux.so
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @nemoobc/opencode-termux@1.20.16.
See all versions of @nemoobc/opencode-termux for other recorded verdicts.
- Review the evidence and your use of @nemoobc/opencode-termux@1.20.16 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.