registry / @tsuga/cli / 1.141.0
@tsuga/cli@1.141.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 10h ago · by lpm-firewall-aiThe flagged subprocess and outbound request implement CLI usage reporting. The code gates reporting on saved or explicit consent, or asks interactively, and the reviewed payload does not include command output or credentials.
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 command completes and telemetry is enabled by the saved choice or TSUGA_TELEMETRY; without either, an interactive prompt asks first.
Impact
The report supports usage analysis and includes command flags and trace/span data; the reviewed path does not send command output or discovered credentials.
Mechanism
The CLI sends a bounded usage report in a detached Node subprocess to the configured Tsuga API URL.
AI rationale
The flagged subprocess and outbound request implement CLI usage reporting. The code gates reporting on saved or explicit consent, or asks interactively, and the reviewed payload does not include command output or credentials.
Network endpoints1
Configured Tsuga API URL (resolveApiUrl)
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/cli.js as the tsuga command-line entry point.
- Telemetry asks whether to send usage data, saves the user's choice, and otherwise sends only when consent is enabled or previously saved.
- The report includes the CLI version, platform, Node version, trace identifiers, command flags, and spans; the background POST uses the configured Tsuga API URL.
- The bundled POST subprocess is started with ignored standard streams and sends the telemetry payload.
Evidence against
- The telemetry path is opt-in through a prompt or an explicit TSUGA_TELEMETRY=1/true setting.
- The inspected telemetry fields contain command flags and span data, not command output or 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.141.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.141.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.