@trayai/helix-cli@1.6.0
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends runtime telemetry to Tray with project identifiers and names, and I found no disclosure in the README; `DO_NOT_TRACK` provides an opt-out. The source does not support the scanner’s credential-redirection or command-output-exfiltration claims, so this warrants a warning rather than a block.
Decision evidence
public snapshot- Runtime analytics records CLI event, outcome, error class and duration alongside OS, runtime, locale, timezone, workspace and project identifiers/name.
- The CLI sends analytics to the Tray API using the user's stored Tray token; `DO_NOT_TRACK` disables it.
- Login and development commands invoke the analytics wrapper when run.
- No analytics disclosure was found in README.md.
- The CLI’s analytics endpoint is Tray’s own service, and the collected fields do not include credentials or file contents.
- Analytics is opt-out through `DO_NOT_TRACK=1` or `true`.
- The package export is a small module exporting error classes; the flagged CLI is the executable entry point.
- The observed child-process helper runs Git commands to detect the default branch and captures their output for that purpose.
Source & flagged code
8 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to @trayai/helix-cli@1.6.0.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@1.6.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.