@tsuga/cli@1.81.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe scanner’s execution and network signals correspond to the CLI’s telemetry reporter. Source inspection shows a consent gate and a Tsuga API telemetry endpoint, with no confirmed attack behavior.
Decision evidence
public snapshot- package.json exposes dist/cli.js as the CLI entrypoint and defines no lifecycle hooks.
- dist/cli.js sends run telemetry only after saved consent, an interactive prompt, or the TSUGA_TELEMETRY override.
- The telemetry request posts run data to the Tsuga API’s /v1/cli-runs endpoint.
- The request uses a short Node subprocess to send the telemetry payload; the inspected source shows no unrelated recipient or secret collection.
Source & flagged code
16 flaggedFindings
Affected versions and remediation
This report applies to @tsuga/cli@1.81.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.81.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.