@trayai/helix-cli@1.15.0
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends undisclosed runtime analytics that can include a locally chosen project name, so this warrants a warning under the telemetry rules. The request uses the Tray API and login token, and I found no evidence of the reported fixed-gateway credential redirect.
Decision evidence
public snapshot- The CLI sends runtime events to the region-resolved Tray API at /private/v1/helix/analytics using a Bearer token; DO_NOT_TRACK disables sending only when set to 1 or true.
- The analytics payload can include the locally chosen projectName alongside Tray workspaceId and projectId.
- The helix init command supplies the project name and runs through the telemetry wrapper, so this data is sent when that command runs.
- The manifest exposes a CLI and JavaScript entry point, with no install, preinstall, or postinstall script.
- The analytics request goes to Tray’s region-resolved API and uses the Tray login token, consistent with the package’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.15.0.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@1.15.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.