@p4code/cli@0.6.7
⚠ Under reviewP4 Code coding agent server and command-line client
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no install lifecycle and its binary is a user-started CLI, with no concrete attack chain found in the inspected entry. A clean verdict cannot be returned because eleven required citation paths exceed the eight-citation limit.
Decision evidence
public snapshot- package.json names the p4c binary and has no preinstall, install, or postinstall script.
- The required clean citation list has 11 paths while source citations allow at most 8, so a clean verdict cannot be finalized from coverage alone.
- Searches of the bin bundle and listed client chunks found no install hook, eval call, or self-dependency lifecycle chain.
- node:child_process and Claude home-path handling appear in the user-started CLI bundle as product behavior, not as an install-time agent control-surface write.
Source & flagged code
22 flagged · loading sourceSource archives sensitive local configuration and publishes encoded chunks through an authenticated package-registry request.
dist/bin.mjsView on unpkg · L13Source appears to send environment or credential material to an external endpoint.
dist/bin.mjsView on unpkg · L13Findings
Affected versions and remediation
This report applies to @p4code/cli@0.6.7.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.6.7 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.