@tangle-network/sandbox-cli@0.21.14
CLI for Tangle Sandbox operations
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package presents itself as a sandbox operations CLI, has no install hooks, and dispatches graph execution through an explicit command. The flagged credential, network, and process behavior is consistent with its agent workflows; the inspected worker path strips the Tangle API key before spawning agents.
Decision evidence
public snapshot- The manifest describes a Tangle Sandbox CLI, points its executable to bin/tangle.js, and declares no install lifecycle scripts.
- The executable imports the CLI bundle; the bundle starts parsing process arguments, consistent with a command-line entry point.
- Graph execution is exposed as an explicit `graph run` command described as running a saved graph over local subscriptions; its embedded bridge binds to 127.0.0.1 and closes after the run.
- The CLI removes TANGLE_API_KEY from the environment passed to spawned workers.
- The inspected passthrough backend sends configured provider credentials to the corresponding provider endpoint for a selected model.
- The manifest includes cli-bridge as a dependency from a pinned GitHub archive URL.
- The CLI bundle uses filesystem, network, and child-process APIs, which account for several scanner alerts but are used for sandbox and agent operations.
Source & flagged code
7 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.mjsView on unpkgFindings
Affected versions and remediation
This report applies to @tangle-network/sandbox-cli@0.21.14.
See all versions of @tangle-network/sandbox-cli for other recorded verdicts.
- Review the evidence and your use of @tangle-network/sandbox-cli@0.21.14 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.