@p4code/cli@0.8.30
⚠ Under reviewP4 Code coding agent server and command-line client
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected CLI and history-worker paths show product functionality, and the flagged shell and dynamic-function excerpts do not establish an attack. The unresolved runtime dependency sources prevent a clean determination.
Decision evidence
public snapshot- package.json declares @cursor/sdk and playwright-core as runtime dependencies; their source was unresolved in this review snapshot.
- The CLI entrypoint dispatches commands to the package’s CLI module.
- The history worker is reached through a hidden CLI subcommand and accepts session-history operations.
- The shell and dynamic-function matches occur in bundled agent-runtime support and a capability check; the inspected excerpts do not establish a reverse shell or credential transfer.
- No concrete attack behavior was established in the inspected source.
Source & flagged code
14 flagged · loading sourcePackage source references child process execution.
dist/AcpMcpStdioBridge-BuIIHL4p.mjsView on unpkg · L4Source appears to send environment or credential material to an external endpoint.
dist/claudeHistoryWorker-js6Jgg9C.mjsFindings
Affected versions and remediation
This report applies to @p4code/cli@0.8.30.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.8.30 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.