@punks/cli@6.5.1
Harness Intelligence scaffolding CLI
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe scanner signals match ordinary CLI and bundled dependency capabilities in the inspected source. The report submission is presented as an explicit CLI operation and uses the configured Harness control plane; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json maps the CLI names to dist/index.js; the declared dependency is react-devtools-core, whose manifest describes React DevTools and points to its backend bundle.
- The CLI report flow describes a user-run report command and submits a Harness report through the configured control-plane URL.
- The dependency backend is a module export; its manifest names it as the package main entry.
- The dependency standalone bundle contains React runtime code, while its parser chunk exports hook-name and source-metadata parsing functions.
- The parser worker contains Babel code-frame functionality.
- The CLI bundle includes process access, child-process utilities, and network calls, but inspected source ties these to CLI operations and configured service or registry behavior; no concrete credential theft or other attack was established.
- The parser chunk fetches a supplied source URL for parsing; inspected code did not establish a package-selected credential recipient.
Source & flagged code
9 flaggedFindings
Affected versions and remediation
This report applies to @punks/cli@6.5.1.
See all versions of @punks/cli for other recorded verdicts.
- Review the evidence and your use of @punks/cli@6.5.1 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.