@tangle-network/sandbox-cli@0.20.29
CLI for Tangle Sandbox operations
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe fixed sponsor destination is an unresolved risk because the inspected excerpts do not show the associated request contents or recipient safeguards. The scanner's credential-redirection and command-output-exfiltration claims are not established by the inspected source excerpts.
Decision evidence
public snapshot- The manifest exposes dist/index.mjs as the package entrypoint.
- The solve deployment hardcodes a sponsor endpoint on drew-gtr-pro.taild10bfc.ts.net.
- The solve metadata check requires that exact sponsor endpoint, so the destination is package-selected and fixed.
- The inspected excerpts do not establish what data or authorization is sent to the sponsor endpoint.
- The flagged command execution and output handling appear in CLI command paths; the excerpts do not show them being sent to an unrelated recipient.
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.29.
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.29 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.