@p4code/cli@0.8.21
⚠ Under reviewP4 Code coding agent server and command-line client
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe inspected source did not confirm the scanner’s attack claims, but the required clean coverage spans more files than the citation limit permits. Manual review is needed to resolve the broader runtime behavior.
Decision evidence
public snapshot- package.json defines a CLI entry and dependencies, with no lifecycle hooks in the inspected manifest.
- The CLI entry dispatches explicit bridge commands or loads the regular CLI.
- The worker has telemetry controls and queues error reports; this excerpt does not identify the report recipient.
- The P4 MCP registry description says provider configuration files are read for import and projected into P4-started sessions.
- The required runtime locations in the settings assets contain UI code, but do not resolve the broader runtime behavior.
- The inspected manifest has no install-time lifecycle script.
- The inspected excerpts do not establish credential theft, reverse-shell behavior, or unconsented writes to provider configuration files.
Source & flagged code
15 flagged · loading sourcePackage contains a possible secret pattern.
dist/runtime-BuR0otfT.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.21.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.8.21 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.