pennyrouter@0.3.25
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe inspected source supports an integration-management purpose: no npm install lifecycle hook is declared, and the reviewed agent configuration and session behavior is tied to PennyRouter functionality. Scanner indicators alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines start and check scripts, with no install lifecycle hook.
- src/harnesses/codex.test.js tests writing Codex configuration in a temporary home.
- src/launch.js names Codex configuration files by PennyRouter profile.
- src/launch.test.js tests preserving existing Claude Code permissions and status-line settings.
- src/mcp-register.test.js exercises MCP status against a temporary Codex configuration.
- src/statusline.js reads the gateway base and PennyRouter key from Claude settings or process environment.
- src/thread-session-codex.js places session files under the Codex sessions directory.
- src/thread-session.js places session files under the Claude projects directory.
Source & flagged code
7 flagged · loading sourceSource writes installer persistence such as shell profile or service configuration.
src/launch.test.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to pennyrouter@0.3.25.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.25 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.