@punks/cli@6.1.2
Harness Intelligence scaffolding CLI
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source supports explicit CLI agent configuration mutation with automatically approved tools, which the supplied policy classifies as warning-only. The scanner's stronger malware claims were not substantiated by inspected behavior.
Decision evidence
public snapshot- The manifest has no npm install lifecycle hooks or runtime self-dependency.
- The explicit init command prompts for selection in interactive mode; other modes accept the proposal defaults.
- The installer synchronizes a TypeScript tool runtime and writes project-level .codex/config.toml.
- Generated MCP configuration enables selected TypeScript read tools with automatic approval.
- The runtime installation uses npm ci with lifecycle scripts disabled, and configuration merging avoids conflicting user-defined servers.
- The explicit update command reapplies installation using saved project settings without another selection prompt.
- No concrete credential theft, covert command-output export, or obfuscated executable payload was established from the inspected source.
- Agent configuration changes occur through CLI scaffolding operations, rather than npm installation hooks.
Source & flagged code
9 flaggedFindings
Affected versions and remediation
This report applies to @punks/cli@6.1.2.
See all versions of @punks/cli for other recorded verdicts.
- Review the evidence and your use of @punks/cli@6.1.2 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.