@hypequery/cli@1.27.0
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends default-on runtime telemetry, but suppresses its disclosure notice in CI and non-TTY contexts. The payload is constrained and opt-outs exist, so this warrants a warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.
Trigger
A CLI command completes while telemetry is enabled; this includes first-run CI and non-TTY invocations.
Impact
Pseudonymous command and environment usage data is transmitted without a notice in noninteractive contexts; inspected fields do not include credentials, code, or paths.
Mechanism
The CLI sends bounded, allowlisted usage events to its first-party telemetry endpoint. The telemetry notice is only displayed for enabled TTY use outside CI.
AI rationale
The CLI sends default-on runtime telemetry, but suppresses its disclosure notice in CI and non-TTY contexts. The payload is constrained and opt-outs exist, so this warrants a warning rather than a malicious verdict.
Evidence
dist/utils/telemetry/config-store.jsdist/utils/telemetry/notice.jsdist/utils/telemetry/environment.jsdist/utils/telemetry/identity.js$XDG_CONFIG_HOME/hypequery/telemetry.json (or ~/.config/hypequery/telemetry.json)os.tmpdir()/hypequery-telemetry-*/batch.json
Network endpoints1
hypequery.com/api/telemetry
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- Telemetry settings default to enabled when no saved preference exists.
- The disclosure notice is skipped for CI and non-TTY invocations, where telemetry can still be sent.
- The notice describes pseudonymous usage collection and gives users ways to disable it.
- The telemetry context contains runtime, command, and project signals; project identity is hashed.
Evidence against
- Telemetry has command-line and environment opt-outs and a persistent disable setting.
- The inspected telemetry fields are constrained to allowlisted values and omit credentials, code, paths, and raw command arguments.
- Login is an explicit browser authorization flow to the configured Hypequery Cloud origin.
- The dynamic import loads the optional @hypequery/serve peer for the dev command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStrings
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 High7 Medium4 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
MediumAi Review Evidencedist/utils/telemetry/config-store.js
MediumAi Review Evidencedist/utils/telemetry/notice.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hypequery/cli@1.27.0.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.27.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.