registry / @tsuga/cli / 1.124.0
@tsuga/cli@1.124.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 2d ago · by lpm-firewall-aiThis is a Tsuga management CLI with an explicit, configurable usage-telemetry consent flow. Its process execution implements that reporting path; the reviewed excerpts show no credential theft or unrelated collection.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
A CLI run with telemetry enabled by TSUGA_TELEMETRY, saved consent, or an interactive opt-in prompt.
Impact
The report contains CLI/runtime metadata and telemetry spans; the inspected code gates transmission on consent.
Mechanism
The CLI creates a detached Node process to POST a run report to the configured Tsuga API endpoint.
AI rationale
This is a Tsuga management CLI with an explicit, configurable usage-telemetry consent flow. Its process execution implements that reporting path; the reviewed excerpts show no credential theft or unrelated collection.
Network endpoints1
Configured Tsuga API URL + /v1/cli-runs
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a Tsuga resource-management CLI and exposes dist/cli.js as its command entry point.
- Usage reporting is gated by saved consent, TSUGA_TELEMETRY, or an interactive consent prompt; noninteractive runs without consent do not send it.
- The CLI-run endpoint is described as Tsuga telemetry and the report is sent to the configured Tsuga API URL.
- The package manifest has no install, preinstall, or postinstall lifecycle hooks.
Evidence against
- When telemetry is enabled, the CLI starts a detached Node process that POSTs a run report to the resolved API URL.
- The report includes CLI version, platform, Node version, trace identifiers, and spans.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
18 flaggeddist/cli.jsView file
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_oauth
severity = critical
line = 273
Critical
273patternName = github_server_token
severity = critical
line = 273
Critical
Secret Pattern
GitHub server-to-server token in dist/cli.js
dist/cli.jsFindings
9 Critical9 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.124.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.124.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.