@tangle-network/sandbox-cli@0.20.50
CLI for Tangle Sandbox operations
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest exposes a CLI without install lifecycle hooks, and its Hub token flow is tied to Hub execution and approval. The scanner signals did not establish credential forwarding to an unrelated recipient or another concrete attack.
Decision evidence
public snapshot- package.json identifies a CLI package with a command entry point and no install lifecycle hook.
- The CLI passes its API key and base URL configuration into Hub client construction.
- The Hub SDK sends action requests to Hub endpoints; capability approval requires an explicit approve option, and minted or approved tokens are used for the requested Hub execution.
- The inspected dependency manifests and entry files identify the expected Tangle SDK packages; no attack behavior was established in the reviewed source.
- The flagged credential flow uses Hub-specific approval and execution endpoints, with action and connection checks; it does not establish forwarding to an unrelated recipient.
- The static hints about command execution and output transfer were not sufficient to establish an attack in the inspected source.
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.50.
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.50 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.