@p4code/cli@0.6.54
P4 Code coding agent server and command-line client
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest has no lifecycle hook, and the inspected suspicious-looking helper installation is part of a generated device-helper path rather than package installation. The flagged agent-related asset locations describe application features, and the inspected source did not establish credential exfiltration or malicious control-surface mutation.
Decision evidence
public snapshot- package.json defines a CLI entry point and no install lifecycle hook.
- The indexed `claude.md` entry is part of a file-type mapping.
- The preview asset describes user-scope memory and agent-file operations as application tools.
- The executable’s helper installation is in a generated device-helper script and runs only when that helper is not already installed.
- The flagged adapter files import the shared PTY adapter; the flagged client chunks import application modules.
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.54.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.6.54 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.