@tangle-network/sandbox-cli@0.21.64
CLI for Tangle Sandbox operations
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged credential flow requires explicit native Claude authorization and stores the token through the Sandbox API; the subprocess has Claude credentials and base-URL variables cleared. The unusual Solve sponsor host is used in a deployment configuration checked against trusted values, and the manifest has no install lifecycle script.
Decision evidence
public snapshot- The manifest identifies this as the Tangle Sandbox CLI and lists build, development, type-check, and test scripts; it has no install lifecycle script.
- Claude subscription enrollment prompts the user to authorize through Claude’s native browser, then stores the token through the Sandbox API.
- The spawned Claude CLI has Claude credential and base-URL environment variables cleared.
- The Solve sponsor URL is a fixed endpoint, and the source checks Solve metadata against the trusted deployment configuration.
Source & flagged code
8 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.mjsView on unpkgFindings
Affected versions and remediation
This report applies to @tangle-network/sandbox-cli@0.21.64.
See all versions of @tangle-network/sandbox-cli for other recorded verdicts.
- Review the evidence and your use of @tangle-network/sandbox-cli@0.21.64 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.