@trayai/helix-cli@1.17.0
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source confirms default runtime analytics sent to Tray, including the `helix init` project name even though the changelog says command arguments are excluded. This is suspicious telemetry, not evidence of credential exfiltration or a malicious install hook.
Decision evidence
public snapshot- The CLI sends authenticated analytics to the configured Tray regional API at `private/v1/helix/analytics`, with a `DO_NOT_TRACK` opt-out.
- The analytics schema includes command event, outcome, error class, duration, runtime and platform details, locale, timezone, and project metadata.
- On `helix init`, the CLI includes a `projectName` derived from the command’s project-name argument.
- The changelog discloses usage analytics but says command arguments are not included; the init project name is nevertheless sent.
- The manifest has no install lifecycle scripts, and the package import entry exports SDK errors rather than starting the CLI.
- The login flow requires an interactive terminal; the source shows no automatic credential redirect to an unrelated host.
- The subprocess helper runs bounded metadata queries such as `git symbolic-ref`; the reviewed code does not send their output to a network endpoint.
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.17.0.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@1.17.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.