registry / @tsuga/cli / 1.74.0
@tsuga/cli@1.74.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe flagged subprocess and network behavior implements opt-in CLI usage reporting, with destination restrictions and no inspected flow of command output or credentials into the report. The secret-like match is part of an embedded credential-pattern catalog, and the package manifest declares no install lifecycle hook.
Static reason
One or more suspicious static signals were detected.
Trigger
A CLI run may report usage after saved consent, an interactive prompt, or an explicit TSUGA_TELEMETRY opt-in.
Impact
No command-output or credential exfiltration was established in the reviewed paths.
Mechanism
The report sends command and run metadata through a POST request; the service URL is restricted to Tsuga hosts or loopback.
AI rationale
The flagged subprocess and network behavior implements opt-in CLI usage reporting, with destination restrictions and no inspected flow of command output or credentials into the report. The secret-like match is part of an embedded credential-pattern catalog, and the package manifest declares no install lifecycle hook.
Evidence
package.jsondist/cli.js
Network endpoints5
api.tsuga.comapi.tsuga-staging.comlocalhost127.0.0.1[::1]
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json maps the tsuga command to dist/cli.js; its declared scripts contain no install lifecycle hook.
- dist/cli.js restricts service URLs to Tsuga hosts or loopback addresses and rejects other destinations before credentials are sent.
- Usage reporting requires saved consent, an interactive prompt, or TSUGA_TELEMETRY set to 1 or true; reports contain run metadata and use a POST sender.
- The credential-looking patterns in dist/cli.js appear as examples in a credential detection catalog, not as usable credentials.
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.74.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.74.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.