registry / @tsuga/cli / 1.108.0
@tsuga/cli@1.108.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package provides the advertised Tsuga CLI and has no install lifecycle hook. Its telemetry is consent-gated and reports successful CLI runs to Tsuga, which is consistent with the package’s purpose.
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 follows a successful CLI run only when the user has enabled it or accepts the interactive consent prompt.
Impact
Opted-in usage data is reported to Tsuga; no malicious behavior was identified.
Mechanism
A background Node process posts CLI run data to the Tsuga API endpoint /v1/cli-runs.
AI rationale
The package provides the advertised Tsuga CLI and has no install lifecycle hook. Its telemetry is consent-gated and reports successful CLI runs to Tsuga, which is consistent with the package’s purpose.
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 package is a Tsuga resource-management CLI, with dist/cli.js as its executable entry point.
- Telemetry is sent only when previously enabled or after an interactive consent prompt; the prompt result is saved.
- The telemetry request records a CLI run at /v1/cli-runs on the Tsuga API host.
Evidence against
- The manifest has no install, preinstall, or postinstall hook.
- The telemetry reporter runs only after a successful command and sends usage data, not command output.
- The bundled process execution supports CLI functionality and the opt-in telemetry request.
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.108.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.108.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.