@hs-x/cli@0.4.13
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 flagged credential flow uses an HS-X machine secret generated locally and sends it with deployment metadata only after a user-authorized live deploy. The package has no install hook, and its runtime telemetry is limited, disclosed, and opt-outable.
Decision evidence
public snapshot- The manifest defines CLI entry points and build scripts, with no install lifecycle hook.
- Deploy asks for mutation consent and requires explicit consent in non-interactive mode.
- The machine bearer secret is generated locally when no configured or saved secret exists.
- A deploy event is sent only after a successful live, non-dry-run deployment; it carries the HS-X machine secret and deployment metadata to the control plane.
- Runtime telemetry reports command and runtime metadata; the CLI discloses it and provides opt-out controls.
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.13.
See all versions of @hs-x/cli for other recorded verdicts.
- Review the evidence and your use of @hs-x/cli@0.4.13 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.