registry / @hypequery/cli / 1.25.1
@hypequery/cli@1.25.1
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe inspected entry point dispatches documented CLI commands, with no install lifecycle hook. Authentication and deployment requests are tied to explicit commands and Hypequery endpoints; telemetry is first-party, bounded, and supports opt-outs.
Static reason
One or more suspicious static signals were detected.
Trigger
CLI invocation; login and deployment network actions require their corresponding commands.
Impact
Expected CLI operations and limited usage telemetry; no source evidence of credential exfiltration or unrelated automatic actions.
Mechanism
Telemetry sends validated usage events to Hypequery's first-party endpoint when enabled. Login exchanges an authorization code with the selected Cloud origin, and deployment reads send the supplied token to a validated deployment endpoint.
AI rationale
The inspected entry point dispatches documented CLI commands, with no install lifecycle hook. Authentication and deployment requests are tied to explicit commands and Hypequery endpoints; telemetry is first-party, bounded, and supports opt-outs.
Evidence
dist/utils/cloud-credential-store.js
Network endpoints2
cloud.hypequery.comhypequery.com/api/telemetry
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a CLI and has no preinstall, install, or postinstall script.
- Cloud login is an explicit command and sends its authorization exchange to the configured Hypequery Cloud origin.
- Usage telemetry is skipped when disabled or opted out, and the default endpoint is the first-party Hypequery endpoint.
- Telemetry events are bounded and identify an installation; the transport disables personal profiles and GeoIP.
- Deployment credentials are sent as bearer tokens only to a validated live deployment URL when that feature is invoked.
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 High5 Medium6 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
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @hypequery/cli@1.25.1.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.25.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.