@tangle-network/sandbox-cli@0.20.46
CLI for Tangle Sandbox operations
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe suspicious network and credential indicators resolve to user-invoked Hub execution and telemetry workflows. The reviewed token flow targets the configured Hub endpoint and is tied to the requested action; no concrete malicious behavior was established.
Decision evidence
public snapshot- package.json identifies a CLI entrypoint, and its scripts contain no install lifecycle hook.
- The Hub SDK obtains a token for the requested action and connection, then sends it with that action’s execution request.
- Capability-token approval is retried only when the caller enables approval, and the returned approval is checked against the requested action and connection.
- The CLI supplies the Hub client’s configured base URL and authentication; the SDK sends requests to that base URL.
- The telemetry writer prompts before changing a shell configuration file, and the reviewed dependency paths contain SDK, interface, schema, and telemetry support code.
- The CLI includes network, subprocess, and agent telemetry features, but the inspected paths tie them to user-invoked workflows and configured destinations.
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.46.
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.46 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.