pennyrouter@0.3.18
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe source shows agent configuration changes during an explicit user-run install, without an npm lifecycle trigger or a confirmed malicious chain. This is a guarded agent integration capability, so a warning is appropriate.
Decision evidence
public snapshot- The package exposes a CLI and declares no preinstall, install, or postinstall hook.
- The CLI dispatches an explicit `install` command to its installer.
- The installer configures Claude Code statusline settings and writes a launch settings file.
- The statusline code reads Claude settings and derives gateway credentials from their environment block.
- The inspected configuration behavior is reached through the explicit CLI install command, not an npm lifecycle hook.
- The source describes the statusline request as a gateway status fetch using the configured gateway and key.
Source & flagged code
6 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.18.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.18 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.