pennyrouter@0.3.20
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found a user-invoked agent configuration capability that installs a statusline wrapper, which merits a warning under the agent integration policy. The source did not establish a concrete attack or an automatic npm installation trigger.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and has no preinstall, install, or postinstall script.
- Claude statusline configuration is explicitly invoked by the package's harness setup flow.
- The statusline setup preserves a user command by wrapping it and changes the settings object to invoke PennyRouter's script.
- The launcher derives agent configuration paths from the user's home or configured Codex home.
- The Codex and Claude session helpers map to their expected local session directories.
- CodeGPT setup is manual and reports no configuration file to mutate.
- Inspected integration tests use temporary home directories for fixture configuration.
- The CLI imports child process and filesystem APIs; these imports alone do not establish malicious behavior.
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.20.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.20 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.