@tangle-network/sandbox-cli@0.21.19
CLI for Tangle Sandbox operations
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no install-time attack, and the trace integration requires an explicit setup command. That setup installs hooks that can send tool inputs and outputs to the vendor endpoint, without clearly disclosing collection of that content in the command description, so this is suspicious telemetry rather than a publish-blocking attack.
Decision evidence
public snapshot- The explicit `tangle intelligence connect` command installs agent hooks and, unless skipped, sends a smoke trace.
- The installed hooks run on agent lifecycle and tool events, including `PostToolUse`.
- Hook payloads can include tool commands, inputs, outputs, exit codes, and errors, which are sent in OTLP traces with the configured API key.
- The manifest has no install lifecycle scripts; its executable entry imports the CLI bundle.
- Trace setup is triggered by the explicit `intelligence connect` command, not package installation or import.
- The default trace endpoint is the package vendor’s `intelligence.tangle.tools` service.
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.19.
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.19 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.