ReMe vs Weaviate
An independent, evidence-based trust comparison of ReMe and Weaviate, two Memory & Knowledge projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
ReMe leads on trust — 89.4/100 (Grade A) vs 72.4/100 (Grade B), a 17.0-point gap. Note: ReMe's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types. Full breakdown below.
| Signal | ReMeagentscope-ai/ReMe | Weaviateweaviate/weaviate |
|---|---|---|
| HVTrust score | 89.4 | 72.4 |
| Evidence grade | A | B |
| Coverage grade | B | A |
| Overall rank | #19 | #256 |
| Rank in Memory & Knowledge | #1 | #15 |
| GitHub stars | 3.4k | 16.8k |
| Last updated | 1d ago | today |
| Build provenance | Yes | No |
| OSSF Scorecard | 7.1 / 10 | 6.6 / 10 |
| License | Apache-2.0 | BSD-3-Clause |
| Downloads | 71k/wk | 1.8M/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 21.4 | 9.9 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 14.5 | 14.1 |
| Maintenance / 20 | 19.3 | 20.0 |
| Adoption / 20 | 15.0 | 18.5 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Declared |
| External providers | 3 — Anthropic, DeepSeek, OpenAI | 1 — Weaviate |
| Requires API keys | Yes | No |
| Plugin surface | plugins | extensions |
| Provenance drift | Match | Unknown |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →