registry / @hypequery/cli / 1.25.2
@hypequery/cli@1.25.2
⚠ Under reviewCLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe inspected source shows a cloud-bound login flow and origin checks for stored deployment endpoints, with no confirmed attack. The imported deployment-target validator's source is unavailable in the snapshot, so its behavior remains unresolved.
Static reason
One or more suspicious static signals were detected.
Trigger
Login or deployment commands that invoke the dependency's target validator.
Impact
The validator's behavior could not be assessed; the reviewed CLI code alone did not establish malicious behavior.
Mechanism
The CLI calls validateProtocolDeploymentReleaseTarget from @hypequery/protocol, whose implementation could not be inspected here.
AI rationale
The inspected source shows a cloud-bound login flow and origin checks for stored deployment endpoints, with no confirmed attack. The imported deployment-target validator's source is unavailable in the snapshot, so its behavior remains unresolved.
Evidence
package.jsondist/commands/login.js
Network endpoints1
cloud.hypequery.com
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares @hypequery/protocol 0.23.0, and the login command imports its deployment-target validator; that dependency's source was not present in the inspected snapshot.
- The inspected CLI source defaults login to cloud.hypequery.com and revalidates stored deployment endpoints against the credential's cloud origin.
- The inspected credential resolver requires an explicit endpoint and HYPEQUERY_API_TOKEN together; no concrete attack was established in the reviewed source.
Evidence against
- The login flow posts to the CLI token route on its normalized cloud origin and saves the resulting credential.
- The stored deployment profile is revalidated when loaded.
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 Dependency Evidencepackage.json
LowSuspicious Dependency Evidencedist/commands/login.js
Affected versions and remediation
This report applies to @hypequery/cli@1.25.2.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.25.2 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.