@hypequery/cli@1.16.3
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection shows a normal user-invoked analytics CLI with no lifecycle hooks or covert execution path. Static signals map to expected dotenv loading, project-module loading, scaffolding installs, and explicit authenticated deployment actions.
Decision evidence
public snapshot- No npm lifecycle script is declared; package execution is through its CLI bin.
- The bin only loads optional dotenv configuration and parses user CLI arguments.
- Dynamic module loading is used by the explicit dev command to load a user-selected project API module.
- Dependency installation occurs only during the explicit init scaffold command.
- No install-time execution, credential harvesting, or covert exfiltration found.
- Cloud login/deployment network use is user-invoked and restricted to configured Hypequery endpoints.
- Project writes are explicit scaffolding outputs such as .env, generated source, and .gitignore.
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.16.3.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.16.3 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.