@hypequery/cli@1.21.1
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection shows no install-time behavior or unsolicited credential transmission. The token upload is tied to explicit deployment commands and an endpoint selected through CLI configuration, so the scanner's structural and dynamic-loading signals do not establish an attack.
Decision evidence
public snapshot- The manifest exposes a CLI binary and has no install lifecycle hook; runtime dependencies are package-aligned.
- The development command dynamically loads the package's optional first-party `@hypequery/serve/dev` module when invoked.
- Deployment submission is an explicit CLI operation that verifies the local bundle before uploading it.
- Deployment endpoints require HTTPS, except loopback development, which emits a plaintext-token warning.
- The upload sends a bearer token to the selected endpoint; when an explicit endpoint is used, a token must also be provided.
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.21.1.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.21.1 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.