registry / @tsuga/cli / 1.82.0
@tsuga/cli@1.82.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe CLI entrypoint's outbound telemetry is gated by stored or interactive consent, and the API URL validation limits non-local destinations to Tsuga's API hosts. The scanner's process and network signals match this telemetry and CLI functionality; the inspected source does not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A CLI command completes; telemetry sending proceeds only when consent is enabled or granted through the interactive prompt.
Impact
No confirmed unauthorized data transfer or other attack surface was established in the reviewed paths.
Mechanism
The CLI serializes run metadata and spans, then sends them in a background HTTP POST to the configured API URL.
AI rationale
The CLI entrypoint's outbound telemetry is gated by stored or interactive consent, and the API URL validation limits non-local destinations to Tsuga's API hosts. The scanner's process and network signals match this telemetry and CLI functionality; the inspected source does not establish malicious behavior.
Evidence
dist/cli.js
Network endpoints1
api.tsuga.com
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes dist/cli.js as the tsuga command entrypoint.
- dist/cli.js sends run telemetry only after the consent check passes; otherwise it returns without sending.
- Telemetry consent can be saved, or requested interactively only for a successful command in an interactive terminal.
- TSUGA_TELEMETRY accepts explicit true values; the telemetry request is sent to the configured Tsuga API endpoint.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
16 flaggeddist/cli.jsView file
268patternName = github_pat
severity = critical
line = 268
Critical
268patternName = github_pat
severity = critical
line = 268
Critical
268patternName = github_oauth
severity = critical
line = 268
Critical
268patternName = github_server_token
severity = critical
line = 268
Critical
Findings
9 Critical7 High2 Medium4 Low
CriticalCritical Secretdist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
HighChild Processdist/cli.js
HighSame File Env Network Executiondist/cli.js
HighCommand Output Exfiltrationdist/cli.js
HighTrigger Reachable Command Output Exfiltration
Affected versions and remediation
This report applies to @tsuga/cli@1.82.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.82.0 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.