registry / mano-coding / 0.1.54
mano-coding@0.1.54
Mano Coding CLI and toolchain
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package is a CLI with no install lifecycle hook, and the reported npm credential flow matches credentials only to the configured request host and path. The CI trigger code uses named environment variables for its API URL and token, consistent with its pipeline functionality.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI invocation; no install-time hook is declared.
Impact
No malicious impact identified.
Mechanism
Registry credentials are constrained to matching configured hosts and paths. The healthcheck uses its named CI environment variables.
AI rationale
The package is a CLI with no install lifecycle hook, and the reported npm credential flow matches credentials only to the configured request host and path. The CI trigger code uses named environment variables for its API URL and token, consistent with its pipeline functionality.
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 and module entry points and declares no install lifecycle hook.
- The CLI wrapper imports the bundled executable when the CLI is invoked.
- npm credentials from configuration are selected only when the request host matches the credential host and the request path matches its configured path.
- The registry healthcheck code reads its trigger token and API URL from explicitly named environment variables.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
NoLicense
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.54.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.54 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.