mano-coding@0.1.49
Mano Coding CLI and toolchain
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package is a coding CLI, but its npm resolver forwards a globally sourced environment token to metadata-supplied tarball hosts without checking that the host matches the registry. This is a real credential disclosure risk, though it depends on a user-run resolution flow and external metadata, so it warrants a warning rather than a block.
Decision evidence
public snapshot- The resolver falls back to NPM_TOKEN, NPM_AUTH_TOKEN, or MANO_NPM_AUTH_TOKEN and turns the value into a bearer authorization header.
- The resolver obtains the tarball URL from npm metadata and resolves authorization for that URL.
- The package loader forwards the resulting authorization header when fetching the tarball URL.
- The .npmrc credential lookup checks that the configured credential host matches the request host, but the environment-token fallback has no equivalent host check.
- The manifest presents this as a coding CLI and exposes it through a command-line entry point.
- The credential flow runs as part of npm package resolution, a normal CLI function, and requires an environment token to be present.
- The .npmrc credential path is scoped to the requested host and path.
Source & flagged code
7 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/bin.jsView on unpkgFindings
Affected versions and remediation
This report applies to mano-coding@0.1.49.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.49 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.