registry / @hypequery/cli
@hypequery/cli
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
This report shows the evidence for @hypequery/cli@1.28.0. 0 of 29 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe credential flows are tied to user-run Cloud commands and send credentials to the configured Hypequery service. Runtime telemetry is disclosed, limited to defined fields, and has clear opt-out controls.
Static reason
One or more suspicious static signals were detected.
Trigger
Login and deployment requests require the corresponding user-run command; telemetry is sent during CLI command completion when enabled.
Impact
No unauthorized credential transfer or other harmful behavior was found.
Mechanism
Login exchanges a browser authorization code with the configured Hypequery Cloud origin. Runtime telemetry is disclosed, can be disabled, and uses bounded fields and hashed project identifiers.
AI rationale
The credential flows are tied to user-run Cloud commands and send credentials to the configured Hypequery service. Runtime telemetry is disclosed, limited to defined fields, and has clear opt-out controls.
Network endpoints2
cloud.hypequery.comhypequery.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The CLI exposes login as an explicit command and lets the user choose the Cloud origin.
- Login uses a browser authorization flow, exchanges its callback code with that origin, and saves the returned Hypequery credential.
- The runtime telemetry notice says it is pseudonymous, excludes code, SQL, names, paths and credentials, and explains how to disable it.
- Telemetry has an opt-out flag and environment variables; its default endpoint is Hypequery’s own service.
- Project identifiers derived from project metadata are SHA-256 hashes, and telemetry records them as hash-formatted IDs.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/commands/init.jsView file
360patternName = generic_password
severity = medium
line = 360
Medium
dist/utils/project-root.jsView file
34try {
L35: resolved = createRequire(path.resolve(fromFile)).resolve(specifier);
L36: }
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/utils/project-root.jsView on unpkg · L34dist/commands/dev.jsView file
128package = @hypequery/cli; repositoryIdentity = hypequery; dependency = open
L128: try {
L129: const open = (await import('open')).default;
L130: await open(baseUrl);
Findings
1 High6 Medium5 Low
HighCopied Package Dependency Bridgedist/commands/dev.js
MediumSecret Patterndist/commands/init.js
MediumDynamic Requiredist/utils/project-root.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumStripped Provenance Metadatadist/commands/login.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowAi Review Evidencedist/cli.js
Affected versions and remediation
This report applies to @hypequery/cli@1.28.0.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @hypequery/cli@1.28.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.