registry / @tsuga/cli / 1.83.0
@tsuga/cli@1.83.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the bundled telemetry path requires saved consent, an interactive affirmative response, or an explicit environment opt-in. Its endpoint validation and inspected source do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI with telemetry already enabled, accepting its interactive usage-data prompt, or setting TSUGA_TELEMETRY to true.
Impact
Telemetry may disclose CLI usage and runtime metadata after consent; no unconsented disclosure or other attack behavior was established.
Mechanism
The CLI reports usage data through a detached child process after its consent check; API URL validation restricts non-local destinations to Tsuga API hosts.
AI rationale
The manifest has no install lifecycle hook, and the bundled telemetry path requires saved consent, an interactive affirmative response, or an explicit environment opt-in. Its endpoint validation and inspected source do not establish malicious behavior.
Evidence
package.jsondist/cli.js
Network endpoints1
api.tsuga.com
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes dist/cli.js as the CLI entrypoint and contains no lifecycle hook.
- Telemetry sending checks saved consent, prompts in interactive use, and otherwise requires TSUGA_TELEMETRY to be true.
- The telemetry reporter returns without consent and includes CLI version, platform, Node version, and usage spans in its report.
- The configured API URL is validated; credentials are refused for non-local URLs outside the Tsuga API hosts.
Evidence against
- The bundle uses a detached child process and fetch to send usage data when telemetry consent is present.
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.83.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.83.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.