pennyrouter@0.3.36
Install and manage PennyRouter local coding-agent integrations.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest has no npm lifecycle hooks, and the flagged integration code is associated with CLI or feature behavior. The scanner signals do not establish an automatic install-time attack or concrete malicious behavior.
Decision evidence
public snapshot- package.json exposes a CLI but defines no preinstall, install, or postinstall hook.
- Agent configuration and session changes are tied to PennyRouter CLI or feature operations; the inspected source does not establish an automatic npm install trigger.
- The flagged standalone web server imports process and filesystem APIs, but those imports alone do not establish malicious behavior.
Source & flagged code
10 flagged · loading sourcePackage source references child process execution.
standalone/web-demo/server.mjsView on unpkg · L3A single source file combines environment access, network access, and code or shell execution; review context before blocking.
standalone/web-demo/server.mjsView on unpkg · L216Findings
Affected versions and remediation
This report applies to pennyrouter@0.3.36.
See all versions of pennyrouter for other recorded verdicts.
- Review the evidence and your use of pennyrouter@0.3.36 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.