registry / @tsuga/cli / 1.139.0
@tsuga/cli@1.139.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 11h ago · by lpm-firewall-aiThe flagged process and network behavior implements usage reporting, which prompts for consent on interactive successful runs and honors saved consent or the TSUGA_TELEMETRY setting. The manifest has no install hooks, and the inspected flow sends reporting data to the resolved Tsuga API.
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 when telemetry consent is enabled or the user accepts the interactive prompt.
Impact
Usage reporting for Tsuga; the inspected flow does not show unrelated credential or file collection.
Mechanism
The CLI serializes run metadata and spans, then starts a detached Node process that POSTs the payload to the resolved API URL.
AI rationale
The flagged process and network behavior implements usage reporting, which prompts for consent on interactive successful runs and honors saved consent or the TSUGA_TELEMETRY setting. The manifest has no install hooks, and the inspected flow sends reporting data to the resolved Tsuga API.
Network endpoints2
api.tsuga.comapi.tsuga-staging.com
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 CLI for managing Tsuga resources and maps its executable to dist/cli.js.
- Usage reporting checks saved consent and otherwise asks "Send usage data?" only in an interactive successful run; the answer is saved and can be changed later.
- When reporting is approved, the CLI sends run metadata and spans to its resolved API URL.
- The source identifies api.tsuga.com and api.tsuga-staging.com as Tsuga API hosts.
Evidence against
- No install lifecycle scripts are declared.
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.139.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.139.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.