registry  /  @weave-framework/cli  /  1.0.4

@weave-framework/cli@1.0.4

Weave CLI — `weave build`, `weave dev` (watch + live-reload), `weave check`, `weave routes`.

Static Scan Results

scanned 2h ago · by rust-scanner

Static analysis flagged 7 finding(s) at 72.0% confidence. This version is warn-only unless an AI or security-team review confirms malicious behavior.

Static reason
One or more suspicious static signals were detected.

Decision evidence

public snapshot
Behavioral surface
Source
ChildProcessDynamicRequireFilesystemNetwork
Supply chain
HighEntropyStringsUrlStrings
ManifestNo manifest risk signals triggered.
scanned 3 file(s), 113 KB of source, external domains: 127.0.0.1

Source & flagged code

2 flagged · loading source
bin/weave.mjsView file
32L33: const { main } = await import(pathToFileURL(out).href); L34: await main(process.argv.slice(2));
Medium
Dynamic Require

Package source references dynamic require/import behavior.

bin/weave.mjsView on unpkg · L32
dist/cli.jsView file
3406package = @weave-framework/cli; repositoryIdentity = weave; dependency = @weave-framework/mcp L3406: try { L3407: const mcp = await import("@weave-framework/mcp"); L3408: await mcp.runStdioServer();
High
Copied Package Dependency Bridge

Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.

dist/cli.jsView on unpkg · L3406

Findings

1 High3 Medium3 Low
HighCopied Package Dependency Bridgedist/cli.js
MediumDynamic Requirebin/weave.mjs
MediumNetwork
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings