@hypequery/cli@1.19.0
CLI for scaffolding type-safe ClickHouse analytics, semantic datasets, React manifests, and deployments
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe suspicious primitives are normal CLI functionality and are not install-time. Source inspection found no lifecycle hook, self-dependency chain, covert exfiltration, or agent-control mutation.
Decision evidence
public snapshot- The package exposes a user-invoked CLI entry point.
- The development command dynamically imports a project module resolved from the current directory.
- The init command can write a project .env file and invoke the selected package manager.
- Deployment submission sends an explicitly supplied or stored bearer token to a configured endpoint.
- package.json has no preinstall, install, postinstall, or other lifecycle hook.
- There is no runtime dependency on @hypequery/cli itself.
- Dynamic loading occurs for explicit dev, deployment, and MCP commands that load the user's API module.
- Network submission is an explicit deployment command and rejects non-HTTPS endpoints except loopback development.
- No credential harvesting, stealth persistence, broad agent-control writes, or destructive behavior 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.19.0.
See all versions of @hypequery/cli for other recorded verdicts.
- Review the evidence and your use of @hypequery/cli@1.19.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.