registry / mano-coding / 0.1.62
mano-coding@0.1.62
Mano Coding CLI and toolchain
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no install hooks, and its CLI entry point loads the bundled tool only when invoked. Inspected credential handling ties npm auth to the matching registry host; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
CLI use; the healthcheck helper is generated for a configured registry operation.
Impact
No unauthorized credential disclosure, install-time activity, or other attack behavior was found in the inspected paths.
Mechanism
The inspected npm auth path limits credentials to requests matching the configured registry host. The healthcheck helper requires explicit registry variables and posts a healthcheck operation.
AI rationale
The package has no install hooks, and its CLI entry point loads the bundled tool only when invoked. Inspected credential handling ties npm auth to the matching registry host; no concrete attack behavior was found.
Network endpoints2
registry.npmjs.org/CI_API_V4_URL (configured by the user)
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package declares no install, preinstall, or postinstall lifecycle scripts.
- The package entry point exports dist/index.js; the CLI imports the bundled dist/bin.js when the bin is run.
- npm auth entries are matched to the request URL's host before a credential is selected.
- The CLI's registry healthcheck script is generated code that requires explicit registry configuration and a trigger token; it posts only a healthcheck operation.
- Automatic update checks are disabled in CI and can be disabled with AICODING_NO_UPDATE_CHECK; the shown code checks update metadata.
Evidence against
- The CLI bundle contains subprocess execution, filesystem access, and network requests; these are consistent with a coding CLI's package, plugin, and update functions.
- The scanner's credential-to-foreign-host lead points to npm configuration loading; inspected auth selection constrains npmrc credentials to the matching host.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
Source & flagged code
8 flaggeddist/bin.jsView file
1159var EventEmitter = __require("node:events").EventEmitter;
L1160: var childProcess = __require("node:child_process");
L1161: var path3 = __require("node:path");
High
1999}
L2000: const execArgv = process4.execArgv ?? [];
L2001: if (execArgv.includes("-e") || execArgv.includes("--eval") || execArgv.includes("-p") || execArgv.includes("--print")) {
High
72892init_self_upgrade_pipeline();
L72893: DEFAULT_NPM_REGISTRY2 = "https://registry.npmjs.org";
L72894: }
...
L72897: // packages/cli/src/commands/auto-update.ts
L72898: import { spawn as spawn9 } from "node:child_process";
L72899: import { homedir as homedir8 } from "node:os";
...
L72901: async function scheduleAutoUpdateWorker(argv, currentVersion, options) {
L72902: const disabled = argv.includes("--offline") || Boolean(process.env["AICODING_NO_UPDATE_CHECK"]) || Boolean(process.env["CI"]) || argv[2] === "self-upgrade" || argv[2] === "_self-up...
L72903: if (disabled) return;
High
Same File Env Network Execution
Findings
6 High3 Medium6 Low
HighChild Processdist/bin.js
HighShelldist/bin.js
HighSame File Env Network Executiondist/bin.js
HighCommand Output Exfiltrationdist/bin.js
HighKnown Malware Source Similaritydist/bin.js
HighKnown Malware Source Fingerprint Signaturedist/bin.js
MediumDynamic Requirebin/mano-coding.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowEvaldist/bin.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to mano-coding@0.1.62.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.62 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.