registry / @tsuga/cli / 1.77.0
@tsuga/cli@1.77.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe scanner’s command-output exfiltration signal is not supported by the inspected source: the report schema excludes command arguments and output, and sending is consent-gated. The configurable API URL rejects non-Tsuga destinations except localhost, so the reviewed behavior supports a clean verdict.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI can reach the run-reporting path; sending requires the telemetry setting, saved consent, or an interactive affirmative response.
Impact
No confirmed unauthorized data disclosure or other attack surface was established.
Mechanism
The report contains the command path without arguments and runtime metadata, then posts it to the configured, validated API URL.
AI rationale
The scanner’s command-output exfiltration signal is not supported by the inspected source: the report schema excludes command arguments and output, and sending is consent-gated. The configurable API URL rejects non-Tsuga destinations except localhost, so the reviewed behavior supports a clean verdict.
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
- package.json identifies dist/cli.js as the CLI entrypoint.
- The recorded run schema includes the command path without arguments and runtime metadata, not command output.
- The telemetry sender checks the TSUGA_TELEMETRY setting, saved consent, or an interactive consent prompt before sending.
- The configurable API URL is restricted to Tsuga API hosts or localhost; other credential destinations are rejected.
Evidence against
- No source-inspected behavior confirms command-output exfiltration or a hardcoded active secret; the flagged network and process execution are used for consent-gated run telemetry.
- The manifest has no preinstall, install, or postinstall hook.
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.77.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.77.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.