registry / mano-coding / 0.1.59
mano-coding@0.1.59
Mano Coding CLI and toolchain
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged credential flow is npm registry authentication and matches credentials only to the requested registry host. Network and process execution serve the CLI’s stated package and Git workflows; the healthcheck code uses explicitly supplied CI settings and a token in generated script content, with no evidence it runs during installation or import.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI invocation; package import routes to the library entry point. The pipeline healthcheck content is generated for explicit project setup and requires running the generated script.
Impact
No malicious impact identified from the inspected source.
Mechanism
The CLI resolves npm authorization against the requested registry host and performs ordinary package and Git operations. No automatic credential exfiltration or unrelated execution was established.
AI rationale
The flagged credential flow is npm registry authentication and matches credentials only to the requested registry host. Network and process execution serve the CLI’s stated package and Git workflows; the healthcheck code uses explicitly supplied CI settings and a token in generated script content, with no evidence it runs during installation or import.
Network endpoints3
registry.npmjs.orggit.iec.ioCI_API_V4_URL (environment-configured)
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package identifies itself as a CLI and exposes a bin entry; no install lifecycle hook is declared.
- The CLI wrapper imports the bundled command-line entry point when present.
- npm auth candidates are restricted to the host of the requested registry URL.
- The auto-update worker is gated by CLI state and configuration checks.
- The healthcheck trigger source is documented as a token validation operation without writes.
Evidence against
- The CLI bundle uses network access and child-process execution for package, Git, and update workflows.
- The bundle contains a GitLab pipeline healthcheck that sends a token supplied through MANO_REGISTRY_TRIGGER_TOKEN to the configured CI_API_V4_URL when that generated script is run.
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.59.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.59 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.