registry / mano-coding / 0.1.61
mano-coding@0.1.61
Mano Coding CLI and toolchain
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package is a CLI/toolchain with no install lifecycle scripts. The inspected credential flow restricts npm credentials to matching registry hosts, and the trigger-token request is generated for a configured healthcheck operation.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI runs when invoked; its registry healthcheck is part of generated user-configured CI code.
Impact
No unauthorized collection or account action was identified.
Mechanism
The CLI resolves npm credentials for matching registry hosts and the generated healthcheck sends its configured trigger token to the configured GitLab API URL.
AI rationale
The package is a CLI/toolchain with no install lifecycle scripts. The inspected credential flow restricts npm credentials to matching registry hosts, and the trigger-token request is generated for a configured healthcheck operation.
Network endpoints2
registry.npmjs.orgCI_API_V4_URL (configured GitLab API URL)
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a CLI/toolchain and exposes a CLI binary that loads its bundled command implementation.
- npm credentials are selected only when the configured credential host matches the requested registry host.
- The generated registry healthcheck uses an explicitly configured API URL and sends only the trigger token and healthcheck operation.
Evidence against
- There are no install lifecycle scripts in the manifest.
- The CLI’s command runner is invoked through its command-line entry point.
- No source evidence showed credentials being sent to an unrelated host or an attack running automatically.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
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.61.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.61 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.