@p4code/cli@0.8.13
⚠ Under reviewP4 Code coding agent server and command-line client
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged worker matches are consistent with bundled Claude Code functionality, and no install hook or confirmed attack was found. The native resource-monitor executable could not be analyzed, leaving its behavior unresolved.
Decision evidence
public snapshot- package.json exposes a CLI and declares no lifecycle scripts.
- The flagged Claude config code reads CLAUDE_CONFIG_DIR and defaults to the user's .claude directory.
- P4 describes its MCP registry as P4-owned and says provider configuration is imported.
- The dynamic-code match only probes whether the runtime permits Function construction.
- The CLI dispatches explicit ACP commands to a bridge; the Claude worker accepts caller-provided execution options.
- The package includes a native executable resource monitor whose behavior could not be resolved by the available artifact analysis.
Source & flagged code
14 flagged · loading sourcePackage contains a possible secret pattern.
dist/runtime-CCVFqL3Y.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.13.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.8.13 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.