@tangle-network/sandbox-cli@0.20.39
CLI for Tangle Sandbox operations
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe runtime routes Solve submission requests through a pinned custom sponsor relay whose ownership is unresolved. The inspected path does not establish credential theft or a concrete attack, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The package manifest exposes a CLI that imports the bundled runtime and declares no install lifecycle hook.
- The bundled runtime pins Solve submissions to a custom sponsor relay on drew-gtr-pro.taild10bfc.ts.net.
- Solve submissions use the configured sponsor URL as the wallet transport for signed transactions.
- The Solve API key is read from an environment variable or saved profile; the inspected transaction relay path does not show that key being sent.
- The relay is used for Solve submission transactions, and the reviewed source does not establish credential theft or another concrete attack.
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.39.
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.39 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.