Quivr
Website
An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search, alerts, and plugins for formats, models and business rules.
Is Quivr safe? Promising trust profile, but some evidence still deserves review.
Compare Quivr
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →In detail: Quivr scores 68.6/100 (Grade B), ranked #379 of 1371 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 6.4/10; 100% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How Quivr could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 83.3 A · #11 of 49
- Raise the OSSF Scorecard from 6.4 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +5.4 → 74.0 B · #15 of 49
Chain of custody
Scanners check what the code says. This traces who ships Quivr and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/The-Vibe-Company/quivr, MIT, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 6.4/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies4
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 4SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 10Vulnerabilities 7 -
Published packages Not linked
- PyPI quivr-core Source link isn't a GitHub repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
Changes to this chain
- 2026-10-05 License changed from NOASSERTION to MIT
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Quivr’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Quivr compares in Memory & Knowledge
- #23 Vellum Assistant 69.6 +1.0
- #24 zvec-grep 68.9 +0.3
- #25 Quivr 68.6 this agent
- #26 Pond 67.5 −1.1
- #27 WeKnora 67.4 −1.2
Bars show each HVTrust score; the tick marks Quivr’s 68.6.
Where the 68.6 comes from
HVTrust dimensions vs the Memory & Knowledge average
68.6 / 100 · 100.0% confidenceQuivr Memory & Knowledge average (49 agents)
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
Activity Inputs
94.2 / 100Common questions about Quivr
Does Quivr publish package provenance?
Does Quivr have an OpenSSF Scorecard?
Is Quivr actively maintained?
What license does Quivr use?
Are Quivr's commits signed?
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 →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Quivr'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 Quivr?
For maintainers
HVTrust scores Quivr 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/quivr)
<a href="https://hvtracker.net/agents/quivr"><img src="https://hvtracker.net/badge/quivr.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON