registry / @tsuga/cli / 1.114.0
@tsuga/cli@1.114.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged network and subprocess behavior belongs to the CLI's usage telemetry path, which checks saved consent or prompts the user before sending. The reviewed code records the recognized command path and run metadata; it does not establish credential or command-output exfiltration.
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 may report telemetry after the user has consented or explicitly enabled TSUGA_TELEMETRY.
Impact
The reviewed behavior does not show credential or command-output exfiltration, or unrelated account actions.
Mechanism
The CLI sends run metadata and the recognized command path to the API URL resolved from its configuration.
AI rationale
The flagged network and subprocess behavior belongs to the CLI's usage telemetry path, which checks saved consent or prompts the user before sending. The reviewed code records the recognized command path and run metadata; it does not establish credential or command-output exfiltration.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest identifies this as the Tsuga resource-management CLI and exposes dist/cli.js as its executable.
- Telemetry records the CLI command path and run metadata, then sends the report to the URL resolved from the CLI's API configuration.
- Telemetry is gated by saved consent or an interactive “Send usage data?” prompt; TSUGA_TELEMETRY=true is an explicit opt-in.
Evidence against
- The bundle uses child-process execution, environment access, and network requests, but the reviewed execution path runs a telemetry report rather than sending command output or credentials.
- The bundle includes credential-pattern strings, but the reviewed excerpts do not show collection or transmission of discovered credentials.
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.114.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.114.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.