@hs-x/cli@0.4.0
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 package automatically sends deployment telemetry to its own service after an unlinked Cloudflare deploy, including project and deploy identifiers. This is undisclosed runtime telemetry rather than credential theft, so it warrants a warning rather than a publish block.
Decision evidence
public snapshot- A successful, non-dry-run Cloudflare deploy in an unlinked project triggers the event when a machine secret exists.
- The event sends a machine bearer and deploy details, including project ID, deploy ID and environment, to the resolved control-plane URL; its default is api.hs-x.dev.
- The machine secret is a locally generated bearer capability for machine event access.
- Deploy asks for consent to apply the plan, but that prompt does not identify the separate deploy event.
- The event is tied to a successful deploy, which is the package’s stated purpose.
- The event goes to the HS-X control plane, and the machine secret is locally generated rather than a discovered third-party credential.
- Deploy mutations require user consent.
Source & flagged code
6 flaggedPackage source references a known benign dynamic code generation pattern.
dist/dev/compat-shim.jsView on unpkg · L36Package source references dynamic require/import behavior.
dist/dev/invoke.jsView on unpkg · L174Findings
Affected versions and remediation
This report applies to @hs-x/cli@0.4.0.
See all versions of @hs-x/cli for other recorded verdicts.
- Review the evidence and your use of @hs-x/cli@0.4.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.