registry / @weave-os/router

@weave-os/router

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.

This report shows the evidence for @weave-os/router@0.2.35. 0 of 19 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 3d ago · by lpm-firewall-ai

The manifest has no install lifecycle hooks, and the CLI's no-argument path only opens the setup page. Credential and network flows inspected are tied to explicit setup or login actions and the configured router service.

Static reason

One or more suspicious static signals were detected.

Trigger

The CLI opens the setup page without arguments; installation, login, and configuration changes require explicit commands.

Impact

Expected configuration changes and authenticated router use; no unsolicited credential collection or unrelated data transfer was identified.

Mechanism

The installer writes client configuration and sends router keys to the selected router endpoint; optional login flows enroll provider accounts with the router.

AI rationale

Network endpoints5

router.weaveos.comclaude.aiconsole.anthropic.comauth.openai.comraw.githubusercontent.com/weave-os/router

Decision evidence

public snapshot

AI called this Clean at 93.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The package describes itself as an installer that configures coding clients to use Weave Router.
The only declared npm script is a prepack build helper; there are no install lifecycle scripts.
Running the CLI without arguments opens the hosted setup page and exits; the installer runs when arguments are supplied.
The Windows installer validates the supplied or configured router key against the selected router base URL.
Login enrollment uses an explicit provider login flow and sends the resulting refresh token to the router's authenticated subscription endpoint.
Lifecycle reports contain only an action and client name and are sent to the endpoint resolved from the user's installed configuration.

Evidence against

The package uses child processes for its installer and language-server transport, and makes network requests as part of router setup and use.
A Codex or Claude status helper can periodically fetch an updated helper from the project's GitHub repository.

Behavioral surface

Source

ChildProcessCrypto

Source & flagged code

5 flagged

pi-router/src/lsp-client.tsView file

8L9: import { spawn as nodeSpawn, type ChildProcess, type SpawnOptions } from "node:child_process"; L10: import * as path from "node:path";

High

Child Process

Package source references child process execution.

pi-router/src/lsp-client.tsView on unpkg · L8

windows.jsView file

1#!/usr/bin/env node L2: // Native Windows entrypoint. PowerShell users do not need Git Bash, jq, or L3: // another installation beyond the npx command they already ran. ... L13: L14: const defaultBaseUrl = process.env.WEAVE_ROUTER_URL || "https://router.weaveos.com"; L15: const packageName = process.env.WEAVE_ROUTER_NPM_PACKAGE || "@weave-os/router";

High

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution; review context before blocking.

windows.jsView on unpkg · L1

bin.jsView file

Findings

3 High4 Medium5 Low

HighChild Processpi-router/src/lsp-client.ts

HighSame File Env Network Executionwindows.js

HighSandbox Evasion Gated Capabilitybin.js

MediumNetwork

MediumEnvironment Vars

MediumShips Build Helperuninstall.sh

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

LowAi Review Evidencepackage.json

Affected versions and remediation

This report applies to @weave-os/router@0.2.35.

The versions list below shows the verdict for each recorded version.

Review the evidence and your use of @weave-os/router@0.2.35 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: 2026-11-02 02:16:21.595Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

19 known versions

0.2.35latestshownClean—AllowPublishedNov 2, 2026, 2:12 AM 0.2.34Clean—AllowPublishedNov 2, 2026, 1:41 AM 0.2.32SuspiciousTelemetryWarnPublishedOct 31, 2026, 8:46 PM 0.2.31Clean—AllowPublishedOct 31, 2026, 7:59 PM

registry / @weave-os/router

@weave-os/router

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.

This report shows the evidence for @weave-os/router@0.2.35. 0 of 19 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 3d ago · by lpm-firewall-ai

Static reason

One or more suspicious static signals were detected.

Trigger

The CLI opens the setup page without arguments; installation, login, and configuration changes require explicit commands.

Impact

Expected configuration changes and authenticated router use; no unsolicited credential collection or unrelated data transfer was identified.

Mechanism

The installer writes client configuration and sends router keys to the selected router endpoint; optional login flows enroll provider accounts with the router.

AI rationale

Network endpoints5

router.weaveos.comclaude.aiconsole.anthropic.comauth.openai.comraw.githubusercontent.com/weave-os/router

Decision evidence

public snapshot

AI called this Clean at 93.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The package describes itself as an installer that configures coding clients to use Weave Router.
The only declared npm script is a prepack build helper; there are no install lifecycle scripts.
Running the CLI without arguments opens the hosted setup page and exits; the installer runs when arguments are supplied.
The Windows installer validates the supplied or configured router key against the selected router base URL.
Login enrollment uses an explicit provider login flow and sends the resulting refresh token to the router's authenticated subscription endpoint.
Lifecycle reports contain only an action and client name and are sent to the endpoint resolved from the user's installed configuration.

Evidence against

The package uses child processes for its installer and language-server transport, and makes network requests as part of router setup and use.
A Codex or Claude status helper can periodically fetch an updated helper from the project's GitHub repository.

Behavioral surface

Source

ChildProcessCrypto

Source & flagged code

5 flagged

pi-router/src/lsp-client.tsView file

8L9: import { spawn as nodeSpawn, type ChildProcess, type SpawnOptions } from "node:child_process"; L10: import * as path from "node:path";

High

Child Process

Package source references child process execution.

pi-router/src/lsp-client.tsView on unpkg · L8

windows.jsView file

High

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution; review context before blocking.

windows.jsView on unpkg · L1

bin.jsView file

Findings

3 High4 Medium5 Low

HighChild Processpi-router/src/lsp-client.ts

HighSame File Env Network Executionwindows.js

HighSandbox Evasion Gated Capabilitybin.js

MediumNetwork

MediumEnvironment Vars

MediumShips Build Helperuninstall.sh

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

LowAi Review Evidencepackage.json

Affected versions and remediation

This report applies to @weave-os/router@0.2.35.

The versions list below shows the verdict for each recorded version.

Review the evidence and your use of @weave-os/router@0.2.35 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: 2026-11-02 02:16:21.595Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

19 known versions