registry / @tsuga/cli / 1.78.0
@tsuga/cli@1.78.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe scanner’s command execution and network signals correspond to an opt-in usage telemetry path that sends a bounded run summary. Source shows effective consent checks and API URL restrictions, with no confirmed attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
A CLI command completes and telemetry consent is effective through an environment opt-in, saved setting, or interactive approval.
Impact
The source does not establish secret collection or unconsented disclosure; the telemetry path is gated and restricts its destination.
Mechanism
The CLI starts a child process to POST command-run metadata to the validated Tsuga API URL.
AI rationale
The scanner’s command execution and network signals correspond to an opt-in usage telemetry path that sends a bounded run summary. Source shows effective consent checks and API URL restrictions, with no confirmed attack surface.
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 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares dist/cli.js as the CLI entrypoint and contains no install lifecycle hook.
- The telemetry payload is limited to CLI version, command path without arguments, duration, exit status, error type, OS, Node version, and trace identifiers.
- Telemetry requires TSUGA_TELEMETRY=1/true, saved consent, or an interactive prompt; the prompt result is saved.
- The telemetry request is sent by a child process as a POST of the run summary.
- The API URL validation permits Tsuga API hosts over HTTPS or localhost, and rejects other destinations.
- The CLI entrypoint wires run reporting into its command completion flow.
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.78.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.78.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.