@tangle-network/sandbox-cli@0.20.49
CLI for Tangle Sandbox operations
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook. The flagged credential and subprocess behavior is tied to caller-invoked Hub execution and user-started SSH tunneling, with no unrelated recipient or concrete attack behavior established.
Decision evidence
public snapshot- The manifest points to a CLI and library entrypoint and contains no install lifecycle hook.
- The Hub SDK sends action-scoped capability tokens to its configured Hub endpoint; approval-token use is gated by the caller’s approval option, and execution follows a caller-invoked tool action.
- The CLI passes its API key to the SSH subprocess when a user starts a tunnel; the API base URL is configurable, with the package default pointing to Tangle’s sandbox service.
- The inspected dependency files expose telemetry definitions and shared interfaces; they do not establish an install-time disclosure path.
Source & flagged code
6 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @tangle-network/sandbox-cli@0.20.49.
See all versions of @tangle-network/sandbox-cli for other recorded verdicts.
- Review the evidence and your use of @tangle-network/sandbox-cli@0.20.49 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.