@tangle-network/sandbox-cli@0.21.66
CLI for Tangle Sandbox operations
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged credential and command paths belong to an explicitly invoked sandbox workflow. The API credential is used with the Tangle router for the user-supplied task; no automatic forwarding of other providers’ credentials was found.
Decision evidence
public snapshot- The manifest exposes the CLI through bin/tangle.js and dist/index.mjs.
- The manifest scripts are build, development, type-checking, verification, and tests; it declares no install lifecycle hook.
- The supervisor command requires a user-supplied task and is described as spawning isolated sandbox workers.
- The router defaults to router.tangle.tools and can be overridden with TANGLE_ROUTER_URL.
- The supervisor passes its router the Tangle API key while running the requested task.
- The authentication path uses TANGLE_API_KEY or the Tangle hub capability token.
Source & flagged code
8 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.66.
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.66 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.