registry / @tsuga/cli / 1.95.0
@tsuga/cli@1.95.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 7d ago · by lpm-firewall-aiThis is Tsuga’s CLI, and its command execution and network activity implement usage reporting. The reporting flow checks saved consent or requests it interactively, and sends to the Tsuga API endpoint.
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
A successful CLI run reports only when telemetry consent is already saved, TSUGA_TELEMETRY explicitly enables it, or an interactive user accepts the prompt.
Impact
Telemetry may disclose CLI run metadata to Tsuga after consent; no unrelated credential transfer or harmful action was found.
Mechanism
The CLI launches a detached Node process to POST usage data to the configured Tsuga API’s /v1/cli-runs endpoint.
AI rationale
This is Tsuga’s CLI, and its command execution and network activity implement usage reporting. The reporting flow checks saved consent or requests it interactively, and sends to the Tsuga API endpoint.
Evidence
XDG_CONFIG_HOME/tsuga/config.json, or ~/.config/tsuga/config.json, for saved telemetry consent
Network endpoints1
api.tsuga.com/v1/cli-runs (or the configured TSUGA_API_URL)
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies this as Tsuga’s resource-management CLI and exposes dist/cli.js as its command entry point.
- Usage reporting checks saved consent, asks an interactive user before sending on a successful run, and returns false when the command is noninteractive or unsuccessful.
- The CLI sends usage data to its /v1/cli-runs endpoint on the Tsuga API; the default API host is api.tsuga.com.
- The POST runs in a detached Node process after the telemetry consent check.
Evidence against
- The bundle uses child_process and HTTP POST, which triggered scanner findings; source ties these to consent-gated usage reporting.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
18 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 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.95.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.95.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.