@p4code/cli@0.8.4
P4 Code coding agent server and command-line client
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed shell behavior is consistent with the package’s coding-agent function. The required source paths show ordinary CLI, editor, rendering, and permission-checked account setup behavior; scanner labels alone do not establish an attack.
Decision evidence
public snapshot- package.json declares the p4c CLI entrypoint and no lifecycle scripts.
- The flagged worker location reads Claude configuration environment variables and validates a project directory name; it does not show a configuration write or credential transfer.
- The worker’s bash subprocess runs in the supplied working directory, consistent with the bundled coding-agent shell tool.
- The ChatMarkdown code processes text nodes and resolves in-page links.
- The prompt editor updates local citation and document state.
- Codex account setup submits a provider update only after its form action and a provider-management permission check.
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.4.
See all versions of @p4code/cli for other recorded verdicts.
- Review the evidence and your use of @p4code/cli@0.8.4 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.