@hypequery/cli@1.18.3
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is a CLI with no lifecycle scripts or self-dependency. Its dynamic loading, dependency installation, file writes, and authenticated upload paths are tied to named user commands and align with its stated CLI functions.
Decision evidence
public snapshot- The flagged dynamic import starts the declared Hypequery development server after the user runs the dev command.
- Network submission sends a verified deployment bundle to a user-supplied or authenticated deployment endpoint.
- The manifest exposes a CLI binary but contains no install lifecycle hook.
- No install-time or import-time network, shell, or file-harvesting behavior was found.
- Project writes occur only in explicit scaffold, build, pull, or deployment commands.
- The runtime dependencies do not include this package, so there is no lifecycle self-dependency chain.
- No obfuscation, credential exfiltration, destructive behavior, or AI-agent configuration mutation was found.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/utils/load-api.jsView on unpkg · L79Findings
Affected versions and remediation
This report applies to @hypequery/cli@1.18.3.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.18.3 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.