pennyrouter@0.3.57
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install-time configuration and later automatic package resolution create a real agent extension lifecycle risk, but the behavior is tied to the package's own MCP integration and is not concrete malicious activity. Recommend a warning rather than a block.
Decision evidence
public snapshot- The package has no npm lifecycle hooks; setup starts through its CLI.
- The install flow registers an MCP server for selected harnesses unless the user disables MCP registration.
- The registration points the harness to `npx -y pennyrouter mcp`, which can run when the harness starts.
- The package also installs a managed Claude Code statusline and preserves an existing user command.
- The other inspected target locations concern profile paths, local session handling, or test fixtures; they do not establish a separate attack.
- The MCP entry runs this package's own `mcp` command, and the source describes it as a Threads integration.
- No credential theft, unrelated network recipient, or concrete malicious payload was established from the inspected source.
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.57.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.57 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.