@tangle-network/sandbox-cli@0.21.15
CLI for Tangle Sandbox operations
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe suspicious static findings resolve to intended CLI features: Tangle router use for an invoked supervisor run and an explicitly invoked telemetry connector with disclosed content tiers. The manifest has no install hook, and the bundle entrypoint dispatches CLI arguments rather than performing unrelated actions automatically.
Decision evidence
public snapshot- The manifest exposes a CLI and has no install lifecycle hook; its scripts are for build, development, type checking, and tests.
- The bundled CLI uses Tangle’s router endpoint for its explicitly invoked supervisor command, passing the Tangle API key as that router’s key.
- Agent telemetry is configured through an explicit `connect` command that describes content collection and offers content tiers, including metadata-only.
- The bundle entrypoint parses CLI arguments; no unrelated automatic execution was identified.
- The telemetry connector can export conversation content, and Claude Code’s content tier defaults to `full`, when a user invokes the connector.
Source & flagged code
7 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.15.
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.15 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.