registry / @hypequery/cli / 1.24.1
@hypequery/cli@1.24.1
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe manifest has no install hook. Inspected credential transfers are tied to user-invoked commands and their configured or origin-bound destinations; the flagged dev import loads the optional development server.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs login, logout, or a deployment command; the dev server is loaded when the user runs the dev command.
Impact
No unconsented credential disclosure or other attack effect was established.
Mechanism
Login sends an authorization code to the configured Cloud origin. Stored credentials are sent to their recorded Cloud endpoint, while explicit deployment endpoints require a corresponding caller-supplied token.
AI rationale
The manifest has no install hook. Inspected credential transfers are tied to user-invoked commands and their configured or origin-bound destinations; the flagged dev import loads the optional development server.
Network endpoints2
cloud.hypequery.com127.0.0.1
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/bin/cli.js as the CLI and has no install lifecycle hook.
- Login defaults to Hypequery Cloud or uses a caller-supplied cloud origin; the user invokes the login command to start authorization.
- Login posts the OAuth authorization code to that origin, and logout sends the stored token to its recorded cloud origin.
- Stored deployment endpoints are bound to the token-issuing origin; live reads require the expected submissions path and HTTPS, except for loopback.
- Explicit deployment endpoints require a matching caller-supplied HYPEQUERY_API_TOKEN.
- The dev command loads the optional Hypequery serve package to run the local development server.
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
125package = @hypequery/cli; repositoryIdentity = hypequery; dependency = open
L125: try {
L126: const open = (await import('open')).default;
L127: 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
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @hypequery/cli@1.24.1.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.24.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.