pennyrouter@0.2.33
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 agent configuration changes are part of explicit CLI integration setup, so the package is clean.
Decision evidence
public snapshot- package.json exposes a command-line entry point; its scripts are start and check, with no install lifecycle hook.
- Agent configuration writes are reached through explicit install, update, or launch commands.
- The statusline helper preserves an existing user command when wrapping it and writes the managed setting to the supplied configuration object.
- CodeGPT setup presents manual instructions and does not edit JetBrains settings.
- MCP registry behavior is implemented as a config transformation; thread-session paths locate local session data.
Source & flagged code
6 flagged · loading sourceSource writes installer persistence such as shell profile or service configuration.
src/launch.test.jsView on unpkg · L28Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
Findings
Affected versions and remediation
This report applies to pennyrouter@0.2.33.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.2.33 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.