@trayai/helix-cli@0.112.0
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe analytics endpoint and purpose are disclosed, but the payload includes a project name derived from the `helix init` argument, conflicting with the changelog’s statement that command arguments are excluded. This is a limited runtime telemetry concern, not evidence of credential theft or malware.
Decision evidence
public snapshot- The CLI posts usage events to the environment-selected Tray API at `private/v1/helix/analytics`, using the saved Tray session token.
- The analytics payload includes `projectName`; the `helix init` command accepts a project name or directory argument and derives the event’s project name from it.
- The changelog discloses analytics for `init`, `login`, `dev`, and `deploy`, but says command arguments are not included.
- Analytics is sent to Tray’s own API and only when a saved login token is available.
- The changelog says analytics excludes source code, file paths, and credentials.
- The package recognizes `DO_NOT_TRACK=1` or `true` to suppress analytics.
Source & flagged code
7 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@0.112.0.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@0.112.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.