registry / @tsuga/cli / 1.75.0
@tsuga/cli@1.75.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime telemetry path requires consent and restricts remote API destinations to Tsuga hosts. The flagged process and network primitives are consistent with this CLI behavior, so the package is clean.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI may trigger telemetry reporting after a successful command when consent is enabled or granted interactively.
Impact
The inspected behavior does not establish unauthorized data disclosure or another attack surface.
Mechanism
The CLI sends run metadata through a detached Node helper to the configured Tsuga API endpoint, subject to URL restrictions.
AI rationale
The manifest has no install lifecycle hook, and the inspected runtime telemetry path requires consent and restricts remote API destinations to Tsuga hosts. The flagged process and network primitives are consistent with this CLI behavior, so the package is clean.
Evidence
package.jsondist/cli.js
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 exposes dist/cli.js as the CLI entry point and has no install lifecycle hook.
- The CLI reports run data only after its consent check passes; it sends the report through a detached helper process.
- Telemetry consent comes from an explicit environment opt-in, saved consent, or an interactive prompt after a successful run.
- The API URL validation restricts remote destinations to HTTPS Tsuga API hosts and permits localhost.
Evidence against
- The bundle contains child-process and network calls, but the inspected paths use them for consent-gated CLI telemetry and restrict the remote API destination.
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.75.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.75.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.