@trayai/helix-cli@0.113.0
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends undisclosed runtime analytics to Tray after common commands, and the payload can include a user-supplied project name. The opt-out and first-party destination reduce the risk; I found no evidence for the reported foreign credential redirect or an install-time attack.
Decision evidence
public snapshot- After `init`, `login`, `dev` and `deploy`, the CLI reports success or failure analytics; the payload can include a project name and IDs.
- The analytics payload includes runtime and locale details, project IDs and project name; `DO_NOT_TRACK=1` or `true` disables sending.
- `helix init <project-name>` derives `projectName` from the supplied argument and runs the analytics wrapper.
- The manifest exposes a CLI but declares no install lifecycle hook.
- Analytics uses a Tray API path and a Tray access token; the code does not show sending that token to a foreign host.
- The project archive builder excludes common credential files, environment files and key files.
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.113.0.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@0.113.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.