registry / @tsuga/cli / 1.128.0
@tsuga/cli@1.128.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package is a CLI for managing Tsuga resources. Its run telemetry requires saved consent or an interactive prompt, and the source provides a setting to disable it; the scanner's execution and network findings fit that functionality.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Running the CLI; telemetry is sent only after saved consent or an interactive consent prompt, or when TSUGA_TELEMETRY is enabled.
Impact
Consent-gated usage reporting to the package's own service; no malicious behavior identified.
Mechanism
The CLI records run metadata and POSTs it to the Tsuga API at /v1/cli-runs.
AI rationale
The package is a CLI for managing Tsuga resources. Its run telemetry requires saved consent or an interactive prompt, and the source provides a setting to disable it; the scanner's execution and network findings fit that functionality.
Evidence
${XDG_CONFIG_HOME}/tsuga/config.json
Network endpoints1
${TSUGA_API_URL or https://api.tsuga.com}/v1/cli-runs
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/cli.js as the CLI executable and declares no install lifecycle scripts.
- CLI run telemetry checks saved consent or asks an interactive user before sending; noninteractive runs without consent are skipped.
- Telemetry sends CLI run data to the Tsuga API endpoint /v1/cli-runs, and the endpoint description says it is sent only by opted-in CLIs.
- The CLI provides a config command to turn usage data on or off.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
18 flaggeddist/cli.jsView file
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_oauth
severity = critical
line = 273
Critical
273patternName = github_server_token
severity = critical
line = 273
Critical
Secret Pattern
GitHub server-to-server token in dist/cli.js
dist/cli.jsFindings
9 Critical9 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.128.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.128.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.