registry / @tsuga/cli / 1.93.0
@tsuga/cli@1.93.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged process and network code sends CLI usage telemetry only after consent or an explicit environment override. The separate update check retrieves package metadata from npm and only displays a notice.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry requires saved consent, TSUGA_TELEMETRY=1 or true, or an affirmative first-run interactive prompt. The update check runs during ordinary CLI startup.
Impact
Opted-in users share CLI usage and span metadata with Tsuga; the update check reveals a request to the npm registry. No credential theft or unrelated execution behavior was identified.
Mechanism
The CLI posts run metadata and recorded spans to the Tsuga API. It separately requests the latest package version from the npm registry and displays an update notice.
AI rationale
The flagged process and network code sends CLI usage telemetry only after consent or an explicit environment override. The separate update check retrieves package metadata from npm and only displays a notice.
Network endpoints2
api.tsuga.com/v1/cli-runsregistry.npmjs.org/@tsuga/cli/latest
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 exposes dist/cli.js as the tsuga command-line entry point.
- Usage telemetry is disabled by default in non-interactive runs; an interactive first run prompts, and the choice is saved. The TSUGA_TELEMETRY override enables it only when set to 1 or true.
- When enabled, the CLI sends run metadata and recorded spans to its Tsuga API cli-runs endpoint.
- The update check requests package version metadata from the npm registry and prints an update notice when a newer version exists.
- The README describes the first successful interactive command as prompting once before sending usage data.
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.93.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.93.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.