registry / @tsuga/cli / 1.90.0
@tsuga/cli@1.90.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 7d ago · by lpm-firewall-aiThis is a resource management CLI, and its child-process/network behavior sends usage telemetry behind explicit consent or opt-in. Although flag values can be included, the source does not show automatic credential exfiltration or unrelated activity.
Static reason
One or more suspicious static signals were detected.
Trigger
CLI command completion; telemetry requires saved consent, interactive approval, or TSUGA_TELEMETRY=true.
Impact
Transmits usage metadata and potentially command-line flag values when telemetry is enabled.
Mechanism
The CLI starts a detached Node process to POST telemetry to the Tsuga API.
AI rationale
This is a resource management CLI, and its child-process/network behavior sends usage telemetry behind explicit consent or opt-in. Although flag values can be included, the source does not show automatic credential exfiltration or unrelated activity.
Evidence
dist/cli.js
Network endpoints1
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 identifies this as Tsuga’s resource management CLI and maps its executable to dist/cli.js.
- Run telemetry is sent only after stored consent, an interactive prompt, or the explicit TSUGA_TELEMETRY=true opt-in.
- Telemetry posts to the Tsuga API’s /v1/cli-runs endpoint.
- The telemetry schema limits command information to the command path and bounded metadata; it may include CLI flag values.
Evidence against
- The bundle contains child-process and network code, including a detached process that sends telemetry.
- Telemetry can include command-line flag values, which may contain sensitive information if a user opts in.
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.90.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.90.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.