Weaviate

Weaviate is an open-source vector database that stores both objects and vectors, allowing for the combination of vector

Memory & Knowledge Go Grade B Listed BSD-3-Clause
75.0/100
Rank #92 of 1283
Compare Weaviate

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade A · 4/5 signals
Last push
2026-08-14 · 0d ago
Recent change
Drift Warning Cleared

Is Weaviate safe? Weaviate scores 75.0/100 (Grade B), ranked #92 of 1283 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.7/10; 50% of recent commits are signed; last pushed 2026-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.7/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
89.9
Activity sub-score · out of 100
#8

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 →

Signals refreshed 2026-08-14 06:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-14

Activity & Reach

Stars
16.7k
Forks
1.4k
Last Push
2026-08-14
today
Commits (4 wk)
993
Downloads (7d)
49,619,317
pypi
HN mentions (30d)
1
Open Issues
452
Rank Change
▲1
was #93

Analysis

HVTrust Dimensions vs Memory & Knowledge

75.0 / 100 · 100.0% confidence

Weaviate Memory & Knowledge average (42 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.9 / 25
0.8 above avg 10.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.4 below avg 12.2
Transparency50% declared license · 50% OSSF Scorecard
14.2 / 17
1.7 above avg 12.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
2.3 above avg 17.7
AdoptionLog-scaled stars · package downloads
20.0 / 20
6.4 above avg 13.6

Activity Inputs

89.9 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.7 / 10
OpenSSF Scorecard · scanned Aug 13, 2026
Signed Commits
50%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 10
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 10
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 7
SAST 10
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 1

Is Weaviate safe?

Public supply-chain signals for Weaviate are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Weaviate carries less obvious unverified-evidence risk than projects with thin signals.
Does Weaviate publish package provenance?
No published build provenance is currently detected for Weaviate. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Weaviate have an OpenSSF Scorecard?
Weaviate has an OpenSSF Scorecard score of 6.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Weaviate actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Weaviate use?
Weaviate ships under BSD-3-Clause. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Weaviate's commits signed?
50% of the last 100 commits to Weaviate are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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.

Compare Weaviate head-to-head

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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 Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Weaviate'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.

2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo

Maintain Weaviate?

For maintainers

HVTrust scores Weaviate 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
Rank 3Score 2Listed 1HVTrust 1Drift 1Drift 1
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
2026-07-13
Rank Moved
Rank dropped 14 spots (#99 → #113)
2026-06-05
Drift Warning Raised
Package-provenance drift warning: package metadata no longer clearly points at this repo
2026-05-27
Rank Moved
Rank rose 60 spots (#73 → #13)
2026-05-27
HVTrust Changed
HVTrust up 24.8pts (55.1 → 79.9)
2026-05-27
Activity Score Changed
Activity score up 25pts (65 → 90)
2026-05-26
Rank Moved
Rank dropped 60 spots (#13 → #73)
2026-05-26
Activity Score Changed
Activity score down 25pts (90 → 65)
2026-05-25
Newly Listed
First tracked at rank #13

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 75.0 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/weaviate.svg)](https://hvtracker.net/agents/weaviate)
HTML:
<a href="https://hvtracker.net/agents/weaviate"><img src="https://hvtracker.net/badge/weaviate.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
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.3 · Raw JSON