@weave-os/router@0.2.34
One-command installer that points Claude Code, Codex, opencode, or pi at the Weave Router. For pi it also ships the routing extension, loaded via pi.extensions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and its CLI performs setup when explicitly run. Reviewed credential use is directed to the configured router, while the flagged process execution supports language-server transport.
Decision evidence
public snapshot- package.json declares CLI entry points and a pi extension, with no install, preinstall, or postinstall hook.
- The CLI opens the hosted setup page only when invoked with no arguments; otherwise it runs the installer.
- The installer’s client event reports use the configured router endpoint and a trust gate; the key is sent in a protected header file.
- The off-state event is called from the explicit `off` command path.
- The Windows installer prompts for a Weave Router key or reads its designated environment/config value, then configures the selected client.
- LSP process spawning uses shell:false and is part of the language-server transport.
- The package includes shell and process execution, filesystem writes, and network requests, but these appear tied to explicit installation, configuration, routing, or language-server features.
- The `prepack` script is a packaging-time helper, not an install lifecycle hook.
Source & flagged code
5 flaggedPackage source references child process execution.
pi-router/src/lsp-client.tsView on unpkg · L8A single source file combines environment access, network access, and code or shell execution; review context before blocking.
windows.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @weave-os/router@0.2.34.
See all versions of @weave-os/router for other recorded verdicts.
- Review the evidence and your use of @weave-os/router@0.2.34 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.