@hypequery/cli@1.21.2
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe explicit deployment flow forwards an existing environment token to a configurable endpoint that is not restricted to the intended service. This meets the warning condition for conditional credential exposure, without evidence of a hidden recipient or automatic attack.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the deployment submit command with deployment credentials configured.
Impact
A token supplied through the environment can be exposed to the operator-configured endpoint; the code does not verify that endpoint belongs to HypeQuery.
Mechanism
The endpoint may come from a command option or environment variable, and the upload request places the API token in its bearer authorization header. Arbitrary HTTPS destinations are accepted.
AI rationale
The explicit deployment flow forwards an existing environment token to a configurable endpoint that is not restricted to the intended service. This meets the warning condition for conditional credential exposure, without evidence of a hidden recipient or automatic attack.
Evidence
dist/utils/cloud-deployment-access.jsdist/utils/deployment-upload.jsdist/commands/deploy.js
Network endpoints2
HYPEQUERY_DEPLOYMENT_ENDPOINT--endpoint
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The deployment credential resolver accepts an endpoint option or deployment endpoint environment variable and pairs it with the API token environment variable.
- The uploader sends that token as a bearer credential in a POST to the selected endpoint.
- Endpoint validation allows arbitrary HTTPS destinations and loopback HTTP, without a HypeQuery host restriction.
- Submission is activated by the explicit deployment submit command.
Evidence against
- The uploader rejects non-HTTPS endpoints except loopback development and rejects embedded endpoint credentials.
- No automatic lifecycle hook is declared; the credential forwarding path is a deployment command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/commands/init.jsView file
348patternName = generic_password
severity = medium
line = 348
Medium
dist/utils/load-api.jsView file
79? await importOverride(moduleUrl)
L80: : await import(/* @vite-ignore */ moduleUrl);
L81: }
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/utils/load-api.jsView on unpkg · L79dist/commands/dev.jsView file
117package = @hypequery/cli; repositoryIdentity = hypequery; dependency = open
L117: try {
L118: const open = (await import('open')).default;
L119: await open(baseUrl);
Findings
1 High7 Medium4 Low
HighCopied Package Dependency Bridgedist/commands/dev.js
MediumSecret Patterndist/commands/init.js
MediumDynamic Requiredist/utils/load-api.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencedist/utils/cloud-deployment-access.js
MediumAi Review Evidencedist/utils/deployment-upload.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @hypequery/cli@1.21.2.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.21.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.