registry / mano-coding / 0.1.51
mano-coding@0.1.51
Mano Coding CLI and toolchain
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged environment, network, and process behavior belongs to the CLI’s npm resolution and update functions. The reviewed credential flow scopes npm auth to the registry request, and the package has no install lifecycle hook.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the mano-coding CLI; package resolution and update checks occur through its command flow.
Impact
No malicious collection, unrelated credential transfer, or other attack impact was identified.
Mechanism
The CLI contacts the configured npm registry, defaults to registry.npmjs.org, and only applies npm auth entries matching the requested host and path. Its update worker is gated by configuration and skips offline and CI runs.
AI rationale
The flagged environment, network, and process behavior belongs to the CLI’s npm resolution and update functions. The reviewed credential flow scopes npm auth to the registry request, and the package has no install lifecycle hook.
Network endpoints2
registry.npmjs.orgUser-configured npm registry
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI command through bin/mano-coding.js.
- The CLI launcher imports the bundled CLI when the command runs.
- npm auth configuration is matched to the request host and path.
- npm metadata requests use the configured registry, with the public npm registry as the default.
- The CLI checks for updates when run; auto-update is configurable and its worker skips offline and CI runs.
Evidence against
- The manifest has no install, preinstall, or postinstall lifecycle hook.
- The inspected credential flow is for npm registry requests, not an unrelated collector.
- The package description and CLI commands are consistent with a coding toolchain.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscation
Source & flagged code
7 flaggeddist/bin.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = mano-coding@0.1.47
matchedIdentity = npm:bWFuby1jb2Rpbmc:0.1.47
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/bin.jsView on unpkg1159var 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
Findings
1 Critical4 High3 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/bin.js
HighChild Processdist/bin.js
HighShelldist/bin.js
HighSame File Env Network Executiondist/bin.js
HighCommand Output Exfiltrationdist/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.51.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.51 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.