@punks/cli@4.0.0
⚠ Under reviewHarness Intelligence scaffolding CLI
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspectable package text shows a user-invoked CLI without an install hook, but the required baseline archive is unreadable binary, so a clean citation of its contents cannot be completed. That inspection gap is not itself proof of an attack.
Decision evidence
public snapshot- package.json publishes user bins hi and hint at dist/index.js and has build, test, and release scripts, with no preinstall, install, or postinstall hook.
- dist/index.js starts as a node CLI and is reached when a person runs hi or hint, not during package install.
- The format hook shells out only to git with the hook's arguments when that script is executed.
- The timesheet helper is a standalone script that reads local git history after the caller supplies month, authors, and a repo map.
- dist/baseline/scaffold-baseline.tgz is a binary archive the CLI names as the scaffold baseline, and its bytes could not be read as source, so the archive contents stay unverified.
- Inspectable CLI and helper scripts limit git, file writes, and the npm registry version lookup to user-run commands or later hook scripts.
- No readable entrypoint shows install-time execution, credential export, or a foreign agent-control write.
Source & flagged code
12 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.0.
See all versions of @punks/cli for other recorded verdicts.
- Review the evidence and your use of @punks/cli@4.0.0 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.