registry / @tsuga/cli / 1.92.0
@tsuga/cli@1.92.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe source ties the scanner’s process and network signals to the CLI’s usage telemetry sender, whose data transfer is consent-gated and whose API destination is validated. The inspected source does not support the scanner’s command-output exfiltration claim.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI with telemetry enabled through saved consent, the TSUGA_TELEMETRY opt-in, or an affirmative interactive response.
Impact
Consent-gated usage data is sent to Tsuga’s API, with no confirmed malicious behavior.
Mechanism
The CLI sends collected context and spans in a JSON POST to its validated API destination; this path does not send captured command output.
AI rationale
The source ties the scanner’s process and network signals to the CLI’s usage telemetry sender, whose data transfer is consent-gated and whose API destination is validated. The inspected source does not support the scanner’s command-output exfiltration claim.
Evidence
package.jsondist/cli.js
Network endpoints1
api.tsuga.com
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/cli.js as the CLI entry point and defines no install lifecycle hooks.
- Usage telemetry sends CLI context and recorded spans only after saved consent, an explicit environment opt-in, or an interactive prompt.
- The telemetry sender posts a JSON body; this path does not use command output as its payload.
- The API URL is validated, and the source refuses credentials for hosts outside its approved destinations.
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.92.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.92.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.