@hypequery/cli@1.24.0
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 22d ago · by lpm-firewall-aiSource inspection shows credentials are used in their corresponding user-invoked Cloud or explicitly configured deployment flows. The flagged dynamic import starts the package's development server, and no concrete attack behavior was identified.
Decision evidence
public snapshot- package.json maps the CLI executable to dist/bin/cli.js.
- The login command opens a browser for authorization, then posts the returned authorization code and verifier to the selected Cloud origin.
- Logout is a separate command that sends the stored token to its saved Cloud origin for revocation.
- Deployment reads send a bearer token to a URL derived from the configured endpoint; explicit endpoint and token settings must be supplied together.
- The dev command dynamically imports the Hypequery serve package to start its development server.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/utils/project-root.jsView on unpkg · L34Findings
Affected versions and remediation
This report applies to @hypequery/cli@1.24.0.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.24.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.