@tangle-network/sandbox-cli@0.20.40
⚠ Under reviewCLI for Tangle Sandbox operations
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe inspected credential, telemetry, and subprocess paths are consistent with configured or user-invoked CLI features, and no concrete attack was established. The imported runtime sandbox dependency's source was unavailable, so its behavior cannot be cleared and manual review is warranted.
Decision evidence
public snapshot- The manifest declares @tangle-network/sandbox as a runtime dependency, and the CLI imports and calls its Sandbox API; that dependency's source was unavailable in the supplied snapshot.
- No install lifecycle hook is declared. The flagged subprocess behavior is exposed as an explicit sandbox process command.
- The inspected credential and telemetry paths use configured service destinations; Solve credentials are restricted to the configured Solve host, and Claude Code setup asks before writing its telemetry block.
- The unusual host is labeled as the Solve transaction sponsor, and the CLI checks that competition metadata matches that configured sponsor.
- No concrete credential theft or unconsented install-time behavior was established in the inspected CLI 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.40.
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.40 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.