registry / mano-coding / 0.1.58
mano-coding@0.1.58
Mano Coding CLI and toolchain
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe suspicious bundle code implements npm registry authentication: it selects credentials only for the configured request host and path and uses them for npm metadata or tarball retrieval. The CLI runs in response to its command entry point, and the manifest declares no install lifecycle hooks.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The npm auth flow runs when a CLI operation resolves a package through npm.
Impact
No unauthorized credential transfer or unrelated automatic action was found in the reviewed source.
Mechanism
The resolver reads npm configuration, matches auth entries to the requested URL’s host and path, then uses the matching auth for npm metadata or tarball requests.
AI rationale
The suspicious bundle code implements npm registry authentication: it selects credentials only for the configured request host and path and uses them for npm metadata or tarball retrieval. The CLI runs in response to its command entry point, and the manifest declares no install lifecycle hooks.
Evidence
~/.npmrc<invocationCwd>/.npmrc~/.manorcdist/bin.jsbin/mano-coding.js
Network endpoints3
registry.npmjs.orggit.iec.iothe registry URL configured by the user or CLI
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a CLI/toolchain and exposes `bin/mano-coding.js` as its command entry point.
- Npm configuration is read from the configured user `.npmrc` and the invocation directory’s `.npmrc`.
- Npm auth is selected only when its configured host and path match the requested registry URL.
- The resolver attaches that auth to requests for npm package metadata or tarballs.
- The bundled CLI calls `run(process.argv)` when the command entry point is loaded; no install lifecycle scripts are declared.
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.58.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.58 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.