@p4code/cli@0.8.15
⚠ Under reviewP4 Code coding agent server and command-line client
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe inspected source did not substantiate the scanner’s attack labels, and the package has no install lifecycle script. The bundled native process-monitor executable is unsupported by the available artifact analysis, leaving material behavior unresolved.
Decision evidence
public snapshot- The native resource monitor is used as the terminal process-table provider, but its executable behavior could not be inspected.
- The worker’s dynamic-function match is an empty-function capability check; its worker accepts two named Claude history operations.
- The manifest identifies a CLI entrypoint and lists no lifecycle script; the runtime target defines P4 MCP and plugin registry schemas.
- The scanner’s reverse-shell and credential-exfiltration labels were not confirmed by the inspected source excerpts.
Source & flagged code
14 flagged · loading sourcePackage contains a possible secret pattern.
dist/runtime-CEdmfdaF.mjsView on unpkg · L7859Package source references child process execution.
dist/AcpMcpStdioBridge-BL9bAh79.mjsView on unpkg · L4Findings
Affected versions and remediation
This report applies to @p4code/cli@0.8.15.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.8.15 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.