@punks/cli@5.2.1
⚠ Under reviewHarness Intelligence scaffolding CLI
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspection found a user-invoked scaffolding CLI with no install lifecycle, no self-dependency, and no hidden exfiltration chain. mark_clean is unavailable because required citation coverage exceeds the eight-citation limit, and that limit alone is not attack evidence.
Decision evidence
public snapshot- package.json 5.2.1 exposes bin entries hi and hint at dist/index.js and defines no preinstall, install, or postinstall script.
- The only runtime dependency is react-devtools-core; the package does not depend on its own name.
- dist/index.js is a node CLI shebang bundle, so execution starts when a user runs hi or hint.
- Required clean citation coverage lists 11 paths while sourceCitations allows at most 8, so a clean decision cannot be finalized.
- No install-time hook, eval, remote payload fetch, or credential send sink was found on the package entrypoint.
- Agent directory writes and git or shell helpers sit in user-invoked scaffold and skill scripts, aligned with the scaffolding CLI purpose.
- Registry and GitHub URLs in the bundle are version checks and the published skills source, not an install-time exfiltration path.
Source & flagged code
20 flaggedPackage source references child process execution.
dist/baseline/scaffold-baseline/skills/misc/timesheet/scripts/git-timesheet-evidence.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @punks/cli@5.2.1.
See all versions of @punks/cli for other recorded verdicts.
- Review the evidence and your use of @punks/cli@5.2.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.