@punks/cli@3.1.10
Harness Intelligence scaffolding CLI
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe static malicious label is not supported by the inspected source. The remaining risk is explicit-user-command agent configuration and hook execution, which warrants a warning rather than a block.
Decision evidence
public snapshot- Explicit CLI scaffolding projects hooks into .claude, .codex, .cursor, and .opencode configs (dist/index.js).
- Projected format hook runs local git, formatter, linter, and Node worker commands on edited project files (dist/data/hooks/format-edited-file.mjs).
- Startup scaffold-check hook invokes local hi/hint check and forwards its output to agent harnesses (dist/data/hooks/scaffold-update-check.mjs).
- package.json contains only bin entrypoints; it has no npm lifecycle scripts.
- Entrypoint behavior requires invoking hi/hint; no import-time or install-time execution is declared.
- Registry fetch is an update/version check to registry.npmjs.org; no credential harvesting or arbitrary exfiltration was found.
- The --eval use is a fixed embedded atomic file-publication worker, not decoded remote payload execution.
Source & flagged code
10 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.jsView on unpkg · L151Findings
Affected versions and remediation
This report applies to @punks/cli@3.1.10.
See all versions of @punks/cli for other recorded verdicts.
- Review the evidence and your use of @punks/cli@3.1.10 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.