@trayai/helix-cli@1.3.0
Helix CLI — helix init, helix dev, helix auth
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged CLI functionality is consistent with a Helix deployment tool: runtime analytics is disclosed, constrained, and opt-out, while deployment packaging filters common secrets. The source reviewed did not support the scanner's credential-redirection or command-output-exfiltration claims.
Decision evidence
public snapshot- The package exposes dist/cli.js as the CLI and dist/index.js as its library entry point; package.json contains no install lifecycle hook.
- Runtime analytics is limited to command event, outcome, error class, duration, CLI/runtime details, and project identifiers or name.
- The changelog discloses analytics for init, login, dev, and deploy, and says it excludes source code, command arguments, file paths, and credentials.
- Analytics is sent to the Tray API's private/v1/helix/analytics endpoint only when a login token is available, and DO_NOT_TRACK=1 or true disables it.
- The deploy packager excludes common secrets and credential files, including .env files, SSH keys, and certificate or key files.
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.3.0.
See all versions of @trayai/helix-cli for other recorded verdicts.
- Review the evidence and your use of @trayai/helix-cli@1.3.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.