@trayai/helix-cli@1.18.1
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source shows runtime telemetry enabled by default that includes workspace and project identifiers, with `DO_NOT_TRACK` as an opt-out. Under the review rules, undisclosed runtime telemetry is suspicious; the observed destination and fields do not establish malicious exfiltration.
Decision evidence
public snapshot- The CLI telemetry schema includes command outcome, duration, error class, runtime and locale details, and workspace and project identifiers.
- It posts events to the Tray API path `/private/v1/helix/analytics` using a bearer token.
- A shared wrapper records events around CLI operations; the login command uses that wrapper.
- Telemetry can be disabled with `DO_NOT_TRACK=1` or `DO_NOT_TRACK=true`. It is enabled by default.
- The manifest declares no install, preinstall, or postinstall lifecycle hook.
- The reported event fields are usage and project metadata; the destination is the package’s Tray API service, not an unrelated collector.
- The package exposes a CLI and an import entry point consistent with its stated 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.18.1.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@1.18.1 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.