@trayai/helix-cli@1.2.0
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged credential and network behavior is consistent with authenticated telemetry for the CLI’s own service, not credential redirection or command-output exfiltration. The changelog discloses analytics, and the implementation supports opt-out through DO_NOT_TRACK.
Decision evidence
public snapshot- The manifest exposes a CLI and library entry point, with no install lifecycle hook declared.
- The changelog discloses usage analytics for init, login, dev, and deploy, and says it excludes source code, command arguments, file paths, and credentials.
- The analytics payload is limited to event outcome, runtime details, locale, timezone, and project/workspace identifiers and name; DO_NOT_TRACK disables sending.
- Analytics is sent only when the user is logged in, to the Tray analytics route using the stored Tray access token.
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.2.0.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@1.2.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.