@p4code/cli@0.8.6
P4 Code coding agent server and command-line client
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged worker code inspected supports session history and local shell interaction. The cited configuration and browser fetch locations do not establish an attack surface.
Decision evidence
public snapshot- package.json exposes a CLI and lists dependencies, with no lifecycle scripts.
- The worker handles validated Claude session-history operations and requires a session ID.
- The flagged configuration location reads CLAUDE_CONFIG_DIR and compares resolved paths; it does not modify agent configuration.
- The worker’s shell process uses piped standard input, output and error as a local shell interface.
- The remaining required files show Effect library code and browser fetches for media and file previews.
Source & flagged code
14 flagged · loading sourceSource appears to send environment or credential material to an external endpoint.
dist/claudeHistoryWorker-v_0uyLGp.mjsView on unpkg · L11Source matches reverse-shell style process and socket wiring.
dist/claudeHistoryWorker-v_0uyLGp.mjsView on unpkg · L11Findings
Affected versions and remediation
This report applies to @p4code/cli@0.8.6.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.8.6 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.