registry / mano-coding / 0.1.53
mano-coding@0.1.53
Mano Coding CLI and toolchain
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package presents itself as a CLI toolchain, has no install lifecycle hook, and the flagged npm credential flow is scoped to the configured request host. Its default self-update behavior is part of the CLI's own update function and checks for an installed CLI before upgrading.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes the mano-coding CLI; registry requests and update checks occur through its commands and startup worker.
Impact
No malicious impact identified. The observed effects are package resolution and the CLI's self-update behavior.
Mechanism
The CLI resolves npm registry configuration, uses host-matched npm credentials for registry requests, and checks for CLI updates.
AI rationale
The package presents itself as a CLI toolchain, has no install lifecycle hook, and the flagged npm credential flow is scoped to the configured request host. Its default self-update behavior is part of the CLI's own update function and checks for an installed CLI before upgrading.
Network endpoints2
registry.npmjs.orggit.iec.io
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a CLI and declares build, test, and release scripts; it has no install lifecycle hook.
- The executable imports the bundled CLI when invoked.
- npm authentication entries are applied only when their configured host matches the request host.
- Package metadata requests use the selected npm registry and pass the matching authorization header to that request.
- The CLI has an auto-update worker that checks for a global installation before upgrading it.
Evidence against
- The auto-update worker is scheduled by default during CLI startup, with offline, CI, and environment-variable opt-outs.
- The CLI reads npm configuration and credentials to authenticate requests to configured registries.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStrings
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.53.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.53 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.