@p4code/cli@0.8.17
P4 Code coding agent server and command-line client
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install lifecycle scripts, and the inspected flagged source does not establish credential exfiltration or a reverse shell. The dynamic Function match is used in a caught feature check, so the scanner hints do not support a malicious verdict.
Decision evidence
public snapshot- package.json declares a CLI entrypoint and dependencies but no install lifecycle scripts.
- dist/bin.mjs dispatches CLI commands only when the module is the process entrypoint.
- The flagged worker location reads Claude configuration directory settings and compares paths.
- The worker’s new Function use is inside a try/catch feature check that returns a boolean.
- The other required files are Effect and schema library bundles, a client asset bundle, and an MCP response parser.
Source & flagged code
13 flagged · loading sourcePackage source references child process execution.
dist/AcpMcpStdioBridge-BL9bAh79.mjsView on unpkg · L4Source appears to send environment or credential material to an external endpoint.
dist/claudeHistoryWorker-BvaF6m2o.mjsFindings
Affected versions and remediation
This report applies to @p4code/cli@0.8.17.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.8.17 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.