@p4code/cli@0.8.11
⚠ Under reviewP4 Code coding agent server and command-line client
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe inspected JavaScript supports CLI history operations and MCP configuration schemas without establishing an attack. The shipped native process-monitor executable is actively used but could not be analyzed, so its behavior remains unresolved.
Decision evidence
public snapshot- The manifest exposes a CLI binary and its complete dependency object contains no lifecycle scripts.
- The flagged worker location reads Claude configuration and project-name environment variables; the runtime location defines MCP settings identifiers.
- The history worker requires a session ID and accepts only history retrieval or session forking; the CLI passes its method and session ID to it.
- The CLI resolves and launches a resource-monitor executable for terminal process telemetry, but the available offline analysis cannot identify the binary format or behavior.
- The bundled native resource-monitor executable is used by the CLI, and its behavior remains unresolved after offline analysis.
Source & flagged code
14 flagged · loading sourcePackage contains a possible secret pattern.
dist/runtime-2Dbe0RYi.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.11.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.8.11 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.