pennyrouter@0.3.44
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe inspected risk is an explicit CLI update that can restore the package’s own MCP configuration despite a saved opt-out. This supports a warning for agent capability/configuration behavior, but not a publish block.
Decision evidence
public snapshot- The manifest exposes a CLI and lists only start and check scripts; neither is an npm install hook.
- CLI dispatch runs installation only when invoked as a command, and otherwise defaults to install.
- The update path registers the MCP server even if a prior opt-out was saved; a per-run flag can skip registration.
- The package manages its own named MCP entry in Claude Code and Codex configuration.
- The reviewed configuration changes are CLI-driven rather than npm lifecycle-triggered.
- MCP registration checks for conflicts and avoids replacing entries it did not create.
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.44.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.44 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.