@trayai/helix-cli@1.0.0
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends runtime analytics to Tray after selected user-run commands, including workspace and project identifiers, without disclosing that telemetry in the README. The observed data flow does not establish credential exfiltration or other malicious behavior, so this is suspicious telemetry rather than a publish-blocking attack.
Decision evidence
public snapshot- Runtime analytics includes event outcome, CLI version, OS, architecture, Node version, locale, timezone, and workspace/project identifiers and name.
- Analytics is sent to the Tray API’s `private/v1/helix/analytics` endpoint with the user’s Tray bearer token.
- The telemetry helper wraps user-run commands such as `helix init` and `helix dev`; it skips sending only when `DO_NOT_TRACK` is set.
- The README describes deployment uploads and says `.env*`, private keys, and credential files are excluded.
- The observed telemetry fields do not include credentials, file contents, prompts, or command output.
- The package documents that deployment uploads source to the platform and excludes common secret files; this is consistent with the CLI’s 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.0.0.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@1.0.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.