@hs-x/cli@0.4.14
HS-X CLI — init, validate, connect, dev, deploy, promote, rollback, doctor, sync. Installs the `hs-x` command.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe deploy event is sent to the package’s own control plane after an explicit deployment, but it includes persistent and project-specific identifiers beyond the CLI’s stated telemetry fields. Because this event is not covered by the telemetry opt-out, classify it as suspicious telemetry.
Decision evidence
public snapshot- After an unlinked Cloudflare deploy succeeds, the command emits a deploy event by default.
- The event sends a stable machine ID, project ID, deploy ID, environment and worker URL to the HS-X control plane, authenticated with a machine secret.
- The telemetry notice describes only command, exit code, duration and OS/architecture, and claims there is no stable identifier; the deploy event has no visible opt-out check.
- The event is limited to a user-run deploy that actually makes a worker live; dry runs and linked deploys do not take this path.
- The bearer secret is generated for HS-X machine events and sent to the package’s configured control plane.
- Ordinary CLI telemetry has an opt-out, and the deploy event is best-effort with a short timeout.
Source & flagged code
6 flaggedPackage source references a known benign dynamic code generation pattern.
dist/dev/compat-shim.jsView on unpkg · L71Package source references dynamic require/import behavior.
dist/dev/invoke.jsView on unpkg · L187Findings
Affected versions and remediation
This report applies to @hs-x/cli@0.4.14.
See all versions of @hs-x/cli for other recorded verdicts.
- Review the evidence and your use of @hs-x/cli@0.4.14 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.