pennyrouter@0.3.59
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged transfers and configuration changes occur in user-invoked CLI integration flows and are consistent with the package's stated functionality.
Decision evidence
public snapshot- package.json defines a CLI executable and only start and check scripts; it has no install lifecycle hook.
- Agent-related source uses PennyRouter-specific Codex profile paths, reads statusline settings, and maps session files into agent directories.
- MCP configuration identifies managed entries by the PennyRouter command and avoids deleting entries it did not create.
- The CLI obtains provider funding credentials during setup and sends them to the selected gateway using the PennyRouter account key; uninstall paths can request credential removal.
- The CodeGPT harness provides manual setup instructions without writing JetBrains settings; the demo server routes local requests to explicit handlers.
- The credential transport and its callers support configured gateway routing and user-invoked setup; no independent attack behavior was identified.
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.59.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.59 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.