registry / @tsuga/cli / 1.91.0
@tsuga/cli@1.91.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged network and process execution implement CLI usage telemetry, with an explicit environment opt-in or a saved consent choice and an interactive prompt when consent is unset. The reviewed reporting path sends run metadata to Tsuga's API; it does not show command-output exfiltration or unrelated credential theft.
Static reason
One or more suspicious static signals were detected.
Trigger
A CLI command completes and telemetry is enabled by `TSUGA_TELEMETRY` or saved consent; otherwise an interactive prompt asks first.
Impact
The service receives usage metadata for the CLI run; no command output or unrelated credential exfiltration was identified in the reviewed path.
Mechanism
The CLI starts a detached Node process to POST run metadata and spans to the resolved Tsuga API.
AI rationale
The flagged network and process execution implement CLI usage telemetry, with an explicit environment opt-in or a saved consent choice and an interactive prompt when consent is unset. The reviewed reporting path sends run metadata to Tsuga's API; it does not show command-output exfiltration or unrelated credential theft.
Network endpoints1
api.tsuga.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a Tsuga resource-management CLI and maps the `tsuga` command to `dist/cli.js`.
- Telemetry reporting checks for `TSUGA_TELEMETRY=true` or saved consent; without either, it prompts interactively and saves the choice.
- The reporter sends CLI run metadata and spans to the resolved Tsuga API using a POST request; the default API host is `api.tsuga.com`.
- The CLI calls the telemetry reporter after command execution, where the consent check determines whether it proceeds.
Evidence against
- The telemetry is described as an opt-in usage-data feature, and the source implements an interactive consent prompt when no choice is saved.
- The reviewed reporting path sends usage metadata to the package's own Tsuga API; no unrelated destination or command-output upload was identified.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
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.91.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.91.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.