registry / mano-coding / 0.1.33
mano-coding@0.1.33
Mano Coding CLI and toolchain
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic inspection shows a user-invoked template-management CLI with no install-time lifecycle behavior or exfiltration path. The reported dynamic evaluation is embedded AJV schema compilation, not remote response execution.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs a mutating CLI command such as apply with a selected package.
Impact
Selected extension content can modify the chosen project, as intended by the CLI.
Mechanism
User-invoked template installation and manifest task execution.
AI rationale
Static inspection shows a user-invoked template-management CLI with no install-time lifecycle behavior or exfiltration path. The reported dynamic evaluation is embedded AJV schema compilation, not remote response execution.
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- This is a CLI that can fetch extension archives and run their declared tasks after a user invokes an apply command.
- The bundle includes a dynamic Function call in embedded AJV schema-validation code.
Evidence against
- package.json has no preinstall, install, postinstall, or other automatic lifecycle hook.
- Archive downloads are integrity-checked before extraction.
- Task processes use shell false and are restricted to project, template, or staging directories.
- No package code sends harvested environment values, credentials, or command output to a remote endpoint.
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.33.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.33 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.