pennyrouter@0.3.62
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found no npm install lifecycle hook or concrete attack behavior. The flagged configuration changes are part of explicit PennyRouter CLI setup, and the statusline request sends its key to the configured gateway for status retrieval.
Decision evidence
public snapshot- package.json defines no preinstall, install, or postinstall hook; it exposes a CLI entrypoint.
- The CLI runs setup only when the user invokes the install command, and harness configuration writes PennyRouter-specific files.
- Claude statusline setup preserves an existing statusline command for later restoration.
- Install setup changes agent configuration, including Claude Code's statusline setting.
- The statusline can send its PennyRouter key to the configured gateway to retrieve session status.
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.62.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.62 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.