conquery

npm

Is conquery safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for conquery v1.10.0. Trust score: 65/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

conquery Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

conquery Capabilities & Permissions

What conquery can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Network Access

This package makes network requests.

github.comstackoverflow.com
Protocols: http, https

Process Spawning

This package can spawn child processes.

Environment Variables

Accesses the following environment variables.

NODE_ENV

AGENTS.md for conquery

Good instructions lead to good results. brin adds conquery documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

conquery Documentation & Source Code

For the full conquery README, API documentation, and source code, visit the official package registry.

Frequently asked questions about conquery safety

Weekly Downloads

49

Version

1.10.0

License

MIT

Last Scanned

2 days ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: github.com, stackoverflow.com

Process

Spawns child processes

Environment

Accesses: NODE_ENV

Is conquery Safe? | npm Safety Scan - brin