registry / mano-coding / 0.1.32
mano-coding@0.1.32
Mano Coding CLI and toolchain
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner's evaluation finding is from bundled AJV schema compilation, while the network and subprocess features are confined to explicit CLI workflows. The manifest has no install lifecycle hook or self-dependency.
Static reason
One or more suspicious static signals were detected.
Trigger
A user explicitly runs the CLI, including its self-upgrade command.
Impact
No unconsented install-time execution, credential harvesting, exfiltration, or remote code execution was confirmed.
Mechanism
User-invoked CLI management and registry metadata retrieval.
AI rationale
The scanner's evaluation finding is from bundled AJV schema compilation, while the network and subprocess features are confined to explicit CLI workflows. The manifest has no install lifecycle hook or self-dependency.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and has no npm install lifecycle hook or runtime dependency.
- The reported dynamic evaluation is bundled AJV validator generation, not execution of network response content.
- Registry access and package-manager execution belong to an explicit self-upgrade CLI command.
- The upgrade registry is restricted to HTTPS URLs without embedded credentials.
Evidence against
- The CLI can perform a user-invoked global self-upgrade through npm or pnpm.
- The CLI bundle includes network, filesystem, and subprocess features expected for its package-management functions.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
7 flaggeddist/bin.jsView file
49* Constructs the CommanderError class
L50: * @param {number} exitCode suggested exit code which could be used with process.exit
L51: * @param {string} code an id string representing the error
...
L1159: var EventEmitter = __require("node:events").EventEmitter;
L1160: var childProcess = __require("node:child_process");
L1161: var path2 = __require("node:path");
...
L1209: this._outputConfiguration = {
L1210: writeOut: (str) => process4.stdout.write(str),
L1211: writeErr: (str) => process4.stderr.write(str),
...
L1248: * @returns {Command[]}
L1249: * @private
L1250: */
Critical
Remote Response Code Execution
Source passes code obtained from a remote response into a dynamic execution sink.
dist/bin.jsView on unpkg · L491159var EventEmitter = __require("node:events").EventEmitter;
L1160: var childProcess = __require("node:child_process");
L1161: var path2 = __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
Findings
1 Critical5 High4 Medium5 Low
CriticalRemote Response Code Executiondist/bin.js
HighChild Processdist/bin.js
HighShelldist/bin.js
HighEvaldist/bin.js
HighSame File Env Network Executiondist/bin.js
HighCommand Output Exfiltrationdist/bin.js
MediumDynamic Requirebin/mano-coding.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to mano-coding@0.1.32.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.32 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.