registry / @tsuga/cli / 1.84.0
@tsuga/cli@1.84.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource inspection confirms a CLI entrypoint without install hooks and telemetry gated by explicit configuration or consent. The flagged execution and network signals do not establish command-output exfiltration or another attack.
Static reason
One or more suspicious static signals were detected.
Trigger
The user runs the CLI; telemetry transmission additionally requires an enabled setting, saved consent, or an affirmative interactive response.
Impact
No unauthorized collection or transfer was established.
Mechanism
The CLI sends run metadata and spans to its configured API URL after checking telemetry consent. The reviewed command execution path does not send command output.
AI rationale
Source inspection confirms a CLI entrypoint without install hooks and telemetry gated by explicit configuration or consent. The flagged execution and network signals do not establish command-output exfiltration or another attack.
Evidence
dist/cli.js
Network endpoints1
api.tsuga.com
Decision evidence
public snapshotAI called this Clean at 94.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 has no install lifecycle hook.
- The CLI sends usage data only when telemetry is enabled by TSUGA_TELEMETRY, saved consent, or an interactive affirmative prompt; noninteractive runs without consent are skipped.
- Telemetry is sent to the configured Tsuga API URL, whose validation restricts destinations to Tsuga’s HTTPS hosts or localhost.
- The bundle’s entrypoint dispatches parsed CLI arguments; inspected network and subprocess paths show no command-output exfiltration.
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.84.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.84.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.