@punks/cli@4.0.2
Harness Intelligence scaffolding CLI
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic inspection found a normal CLI with no npm lifecycle scripts. Scanner signals stem from a bundled scaffolding archive, explicit project-writing functionality, and a consent-gated self-update check.
Decision evidence
public snapshot- The manifest exposes only user-invoked CLI binaries and contains no install lifecycle hook.
- The registry request fetches only the tagged package metadata version.
- A global package update runs only after an interactive yes-or-no prompt.
- The compressed baseline archive contains readable scaffolding assets, not an opaque executable payload.
- The CLI performs a background self-update version check against the npm registry when users run commands.
- The explicit scaffold and operator commands can write developer-tool configuration into the selected project.
Source & flagged code
10 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@4.0.2.
See all versions of @punks/cli for other recorded verdicts.
- Review the evidence and your use of @punks/cli@4.0.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.