@tangle-network/sandbox-cli@0.21.7
CLI for Tangle Sandbox operations
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged network and process behavior supports the package’s sandbox CLI purpose: the Tangle API key is used by the requested supervisor flow with Tangle’s router, then excluded from worker environments. The manifest and inspected dependency show no install lifecycle hook that would run this behavior automatically.
Decision evidence
public snapshot- The manifest points to a CLI executable and `dist/index.mjs`; its scripts are build, development, and test tasks, with no install lifecycle hook listed.
- The executable imports the CLI module, which parses `process.argv` to dispatch commands.
- The supervisor command uses `https://router.tangle.tools/v1` and passes its API key to that router when supervision is requested.
- Worker environments have `TANGLE_API_KEY` removed before workers are created.
- The package’s router endpoint belongs to the Tangle service named by the package and its repository.
- The CLI can make network requests and run sandbox workers, but the reviewed router flow is tied to the explicit `supervise` command.
- The package includes a pinned GitHub tarball dependency, `cli-bridge`; its inspected manifest lists no install lifecycle hook.
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.7.
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.7 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.