pennyrouter@0.3.71
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and its inspected credential and agent-configuration behavior is part of user-invoked setup for PennyRouter integrations. No concrete attack behavior was found in the flagged paths.
Decision evidence
public snapshot- package.json exposes a command-line entry point and defines no npm lifecycle hooks.
- Claude subscription support is presented as a funding choice; account linking uses a PennyRouter key and the configured gateway.
- The linking helper checks whether the gateway supports linking and whether the account is already bound before sending a Claude Code token to that gateway for account binding.
- The CLI writes managed integration files during explicit setup and preserves existing unowned skill files.
- Remote handoff requires a user remote command and a matching assistant acknowledgment before writing a local handoff request.
- Status display retrieves gateway status into a local cache; CodeGPT setup gives manual instructions rather than editing IDE settings.
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.71.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.71 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.