Registry › Compare › LanceDB vs ReMe

LanceDB vs ReMe

Both are Grade A and 0.8 points apart, so choose on what you weigh most. LanceDB leads on maintenance and adoption, and rests on broader evidence; ReMe leads on supply-chain integrity and transparency. Note: ReMe's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types.

A LanceDB 87.7

Developer-friendly OSS embedded retrieval library for multimodal AI. Search More; Manage Less.

lancedb/lancedb · #46 overall · #3 Memory & Knowledge · coverage A (4/5)

Choose LanceDB if maintenance and adoption matter most.

+4.3Adoption: 1.8M weekly downloads against 9.4k
+1.4Maintenance: last push 1d ago, against 2d ago
A vs BEvidence coverage: 4 of 5 independent signal types, against 3

A ReMe 88.5

ReMe: Memory Management Kit for Agents - Remember Me, Refine Me.

agentscope-ai/ReMe · #35 overall · #1 Memory & Knowledge · coverage B (3/5)

Choose ReMe if supply-chain integrity and transparency matter most.

+1.7Safety / Integrity: 100% of recent commits signed, against 88%
+0.7Transparency: OSSF Scorecard 7.1 against 6.2

Where they differ

19.7

Safety / IntegrityReMe +1.7

21.4

13.8

TransparencyReMe +0.7

14.5

19.9

MaintenanceLanceDB +1.4

18.5

18.1

AdoptionLanceDB +4.3

13.8

-1.8

Runtime calibrationReMe +4.1

+2.3

1 dimension identical: Identity 18.0 · Full evidence table

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.

Full evidence

Signal	LanceDBlancedb/lancedb	ReMeagentscope-ai/ReMe
HVTrust score	87.7	88.5
Evidence grade	A	A
Coverage grade	A	B
Overall rank	#46	#35
Rank in Memory & Knowledge	#3	#1
GitHub stars	11.6k	3.6k
Last updated	1d ago	2d ago
Build provenance	Yes	Yes
OSSF Scorecard	6.2 / 10	7.1 / 10
License	Apache-2.0	Apache-2.0
Downloads	1.8M/wk	9k/wk
Trust dimensions (points earned)
Safety / integrity / 25	19.7	21.4
Identity & provenance / 18	18.0	18.0
Transparency / 17	13.8	14.5
Maintenance / 20	19.9	18.5
Adoption / 20	18.1	13.8
Runtime capability surface (full matrix)
MCP server	—	Implemented
External providers	4 — Amazon Bedrock, Cohere, Google Gemini, …	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.4 →