registry / @tsuga/cli / 1.148.0
@tsuga/cli@1.148.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 7h ago · by lpm-firewall-aiThe package is a Tsuga resource-management CLI. Its reviewed telemetry flow requires explicit opt-in or an interactive consent prompt and sends CLI run data to the Tsuga API; no malicious behavior was identified.
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
An explicit TSUGA_TELEMETRY=1 setting, or an interactive user accepting the usage-data prompt; saved consent governs later runs.
Impact
No unauthorized collection or harmful action was identified in the reviewed telemetry flow.
Mechanism
The CLI sends run metadata and spans to the Tsuga API’s /v1/cli-runs endpoint using a detached Node subprocess.
AI rationale
The package is a Tsuga resource-management CLI. Its reviewed telemetry flow requires explicit opt-in or an interactive consent prompt and sends CLI run data to the Tsuga API; no malicious behavior was identified.
Network endpoints1
Tsuga API base URL resolved by the CLI: /v1/cli-runs
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 describes a Tsuga resource-management CLI and exposes dist/cli.js as its executable.
- Run telemetry is sent only after the CLI has an explicit saved consent choice or prompts an interactive user; TSUGA_TELEMETRY=1 is an explicit opt-in.
- The telemetry request records a CLI run at the Tsuga API’s /v1/cli-runs endpoint and includes run metadata, version, platform, Node version, and spans.
Evidence against
- The entry point uses child-process execution and network requests, but the reviewed execution sends the opt-in telemetry payload and discards subprocess output.
- The scanner’s critical-secret match is in bundled credential-pattern definitions; no secret transmission was identified in the reviewed path.
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.148.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.148.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.