@tangle-network/sandbox-cli@0.21.10
CLI for Tangle Sandbox operations
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged APIs support the package’s CLI functions, and the router defaults to a Tangle host with an environment override. The package declares no install lifecycle script, and the reviewed credential flow showed no unrelated collector or automatic account action.
Decision evidence
public snapshot- The manifest exposes a CLI and lists build, development, type-checking, and test scripts; it declares no install lifecycle script.
- The supervisor workflow passes a router URL and API key to the agent runtime as part of its sandbox-worker task.
- The default router is router.tangle.tools, with TANGLE_ROUTER_URL available to override it.
- The CLI reads TANGLE_API_KEY or TANGLE_API_KEY_FILE for sandbox authentication, and its default sandbox service is sandbox.tangle.tools.
- Before creating a worker, the supervisor removes TANGLE_API_KEY from the worker environment.
- The CLI imports process execution, filesystem, and network capabilities, consistent with its purpose of managing sandboxes and agent workflows.
- The manifest includes cli-bridge as a runtime dependency, pinned to a repository tarball; no package install hook is declared to run it automatically.
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.10.
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.10 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.