pennyrouter@0.3.63
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe flagged agent configuration writes implement package-owned integrations and are reached through the explicit installer, not an npm lifecycle hook. Their effect warrants a warning for agent extension setup, but the inspected code does not establish malicious behavior.
Decision evidence
public snapshot- The manifest exposes a command line entry and defines no npm install lifecycle hook.
- Running the install command registers the package's MCP service unless the user disables registration or requests a dry run.
- The registration creates a package-owned service entry that launches PennyRouter through the package runner.
- The Claude integration writes a managed status display command into the harness settings and preserves an existing user command for restoration.
- The reviewed configuration changes are tied to the package's explicit install command, rather than npm installation.
- The registration skips an absent Claude registry and avoids replacing a conflicting entry it does not manage.
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.63.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.63 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.