Qdrant
Qdrant - High-performance, massive-scale Vector Database and Vector Search Engine for the next generation of AI. Also av
Compare Qdrant
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →Promising trust profile, but some evidence still deserves review.
Is Qdrant safe? Qdrant scores 71.4/100 (Grade B), ranked #130 of 1308 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; recent commits are unsigned; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in Memory & Knowledge
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
HVTrust Dimensions vs Memory & Knowledge
71.4 / 100 · 100.0% confidenceQdrant Memory & Knowledge average (44 agents)
Activity Inputs
93.1 / 100Supply Chain Trust
Is Qdrant safe?
Does Qdrant publish package provenance?
Does Qdrant have an OpenSSF Scorecard?
Is Qdrant actively maintained?
What license does Qdrant use?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Qdrant's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Qdrant?
For maintainers
HVTrust scores Qdrant from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/qdrant)
<a href="https://hvtracker.net/agents/qdrant"><img src="https://hvtracker.net/badge/qdrant.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · crates.io (downloads) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON