pennyrouter@0.3.72
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection found no package lifecycle hook. The credential and agent-configuration behavior is tied to CLI setup and account linking with the configured gateway, so the scanner signals do not establish a malicious attack surface.
Decision evidence
public snapshot- package.json exposes a CLI and has no install lifecycle hook.
- Agent configuration is written during CLI installation or launch; the statusline setup preserves an existing user command, and uninstall can restore it.
- Claude sign-in reads a local Claude account token and sends it to the configured gateway only through the account-linking flow, after the gateway reports linking is enabled.
- Other upstream credentials are sent to the configured gateway’s credential endpoint with the PennyRouter key.
- The inspected integration targets show CLI setup, per-profile configuration, or tests; they do not establish an unconsented install-time attack.
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.72.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.72 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.