ReMe vs Weaviate
ReMe leads on trust: 89.2/100 (Grade A) against 71.9/100 (Grade B), a 17.3-point gap. ReMe leads on supply-chain integrity and provenance; Weaviate leads on maintenance and adoption, and rests on broader evidence. Note: ReMe's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types.
ReMe: Memory Management Kit for Agents - Remember Me, Refine Me.
Choose ReMe if supply-chain integrity and provenance matter most.
- +11.8Safety / Integrity: 100% of recent commits signed, against 8%
- +7.2Identity / Provenance: package provenance attested, against none
Weaviate is an open-source vector database that stores both objects and vectors, allowing for the combination of vector search with structured filtering with the fault tolerance and scalability of a cloud-native database.
Choose Weaviate if maintenance and adoption matter most.
- +3.2Adoption: 1.5M weekly downloads against 92k
- +0.7Maintenance
- A vs BEvidence coverage: 4 of 5 independent signal types, against 3
Where they differ
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.
Full evidence
| Signal | ReMeagentscope-ai/ReMe | Weaviateweaviate/weaviate |
|---|---|---|
| HVTrust score | 89.2 | 71.9 |
| Evidence grade | A | B |
| Coverage grade | B | A |
| Overall rank | #44 | #339 |
| Rank in Memory & Knowledge | #1 | #22 |
| GitHub stars | 3.8k | 17.0k |
| Last updated | today | today |
| Build provenance | Yes | No |
| OSSF Scorecard | 6.5 / 10 | 6.7 / 10 |
| License | Apache-2.0 | NOASSERTION |
| Downloads | 92k/wk | 1.5M/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 20.6 | 8.8 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 14.0 | 14.2 |
| Maintenance / 20 | 19.3 | 20.0 |
| Adoption / 20 | 15.2 | 18.4 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Declared |
| External providers | 2 — Anthropic, OpenAI | 1 — Weaviate |
| Requires API keys | Yes | No |
| Plugin surface | plugins | — |
| 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.4 →