@trayai/helix-cli@0.112.1
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged credential-broker behavior is an explicitly invoked MCP feature using a selected authentication, not automatic credential exfiltration. Runtime analytics are disclosed and opt-out is available, but they include project names that the disclosure does not identify, so this warrants a telemetry warning.
Decision evidence
public snapshot- Runtime analytics are sent to the environment-configured Tray API at `private/v1/helix/analytics`, authenticated with the user’s Tray token.
- Analytics can include `projectName`, which the CLI reads from the project configuration, along with project and workspace IDs.
- The changelog discloses usage analytics for `init`, `login`, `dev`, and `deploy`, but does not mention sending project names.
- Analytics can be disabled with `DO_NOT_TRACK=1` or `DO_NOT_TRACK=true`.
- The changelog says analytics excludes source code, command arguments, file paths, and credentials.
- The credential broker tool is part of an explicitly started MCP server and uses a selected configured authentication for a supplied request.
- The manifest has no install, preinstall, or postinstall hook.
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.112.1.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@0.112.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.