registry / @tsuga/cli / 1.125.0
@tsuga/cli@1.125.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe scanner’s execution and network findings correspond to consent-gated CLI telemetry. Although the report includes command-line arguments, sending usage data is disclosed, consent-controlled, and directed to the package’s own service.
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
Telemetry runs after a CLI command and requires saved consent, an explicit telemetry environment opt-in, or an interactive consent prompt.
Impact
No unauthorized collection or execution was identified. Users can review or change telemetry consent in the CLI configuration.
Mechanism
The CLI posts a JSON usage report to the configured Tsuga API; the API URL validation restricts remote hosts to Tsuga’s API hosts.
AI rationale
The scanner’s execution and network findings correspond to consent-gated CLI telemetry. Although the report includes command-line arguments, sending usage data is disclosed, consent-controlled, and directed to the package’s own service.
Network endpoints2
api.tsuga.comapi.tsuga-staging.com
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The CLI is the package’s declared executable, and the manifest shows no install lifecycle scripts.
- Run telemetry is gated by saved consent or an interactive “Send usage data?” prompt; the package provides a setting to turn it on or off.
- The report includes command arguments, but it is sent as usage telemetry to the configured Tsuga API, whose allowed hosts are restricted.
Evidence against
- Telemetry captures up to 32 command-line arguments, which can contain user-provided values.
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.125.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.125.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.