RegistryCompare › LanceDB vs ReMe

LanceDB vs ReMe

An independent, evidence-based trust comparison of LanceDB and ReMe, two Memory & Knowledge projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

LanceDB leads on trust — 87.1/100 (Grade A) vs 74.7/100 (Grade B), a 12.4-point gap. Full breakdown below.
Signal LanceDBlancedb/lancedb ReMeagentscope-ai/ReMe
HVTrust score 87.1 74.7
Evidence grade A B
Coverage grade A B
Overall rank #29 #92
Rank in Memory & Knowledge #1 #8
GitHub stars 11.1k 3.3k
Last updated today 2d ago
Build provenance Yes No
OSSF Scorecard 6.2 / 10 5.6 / 10
License Apache-2.0 Apache-2.0
Downloads 1.6M/wk 128k/wk
Trust dimensions (points earned)
Safety / integrity / 25 19.6 12.0
Identity & provenance / 18 18.0 10.8
Transparency / 17 13.8 13.3
Maintenance / 20 20.0 19.1
Adoption / 20 18.0 15.3
Runtime capability surface (full matrix)
MCP server Implemented
External providers 5 — Amazon Bedrock, Anthropic, Cohere, … 2 — Anthropic, OpenAI
Requires API keys No Yes
Plugin surface plugins plugins
Provenance drift Unknown Match
Open in the live compare tool → LanceDB profile ReMe profile More Memory & Knowledge →

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 →