@hypequery/cli@1.18.0
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe deployment flow can forward HYPEQUERY_API_TOKEN to an unrestricted, operator-configured HTTPS endpoint. This is a conditional credential exposure risk, so it warrants a warning rather than a block.
Decision evidence
public snapshot- The deployment command accepts an operator-configured endpoint and pairs it with HYPEQUERY_API_TOKEN.
- The upload transport sends that token as a bearer credential to the selected endpoint.
- The transport permits HTTPS endpoints without restricting them to a Hypequery host.
- The endpoint and token must both be explicitly supplied for this configuration path; the inspected code does not show a hidden default recipient.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/utils/load-api.jsView on unpkg · L79Findings
Affected versions and remediation
This report applies to @hypequery/cli@1.18.0.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.18.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.