Registry › Compare › Mem0 vs ReMe

Mem0 vs ReMe

Both are Grade A and 2.7 points apart, so choose on what you weigh most. Mem0 leads on 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 Mem0 86.0

The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.

mem0ai/mem0 · #69 overall · #7 Memory & Knowledge · coverage A (4/5)

Choose Mem0 if adoption matters most.

+5.5Adoption: 488k weekly downloads against 7.5k
A vs BEvidence coverage: 4 of 5 independent signal types, against 3

A ReMe 88.7

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

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

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

+2.0Safety / Integrity: OSSF Scorecard 7.1 against 5.5
+1.3Transparency: OSSF Scorecard 7.1 against 5.5

Where they differ

19.4

Safety / IntegrityReMe +2.0

21.4

13.2

TransparencyReMe +1.3

14.5

18.5

MaintenanceReMe +0.3

18.8

19.2

AdoptionMem0 +5.5

13.7

-2.3

Runtime calibrationReMe +4.6

+2.3

1 dimension identical: Identity 18.0 · Full evidence table

An independent, evidence-based trust comparison of Mem0 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	Mem0mem0ai/mem0	ReMeagentscope-ai/ReMe
HVTrust score	86.0	88.7
Evidence grade	A	A
Coverage grade	A	B
Overall rank	#69	#31
Rank in Memory & Knowledge	#7	#1
GitHub stars	66.3k	3.5k
Last updated	4d ago	today
Build provenance	Yes	Yes
OSSF Scorecard	5.5 / 10	7.1 / 10
License	Apache-2.0	Apache-2.0
Downloads	488k/wk	7k/wk
Trust dimensions (points earned)
Safety / integrity / 25	19.4	21.4
Identity & provenance / 18	18.0	18.0
Transparency / 17	13.2	14.5
Maintenance / 20	18.5	18.8
Adoption / 20	19.2	13.7
Runtime capability surface (full matrix)
MCP server	Implemented	Implemented
External providers	14 — Amazon Bedrock, Anthropic, Cohere, …	2 — Anthropic, OpenAI
Requires API keys	Yes	Yes
Plugin surface	plugins	plugins
Provenance drift	Partial	Match

Open in the live compare tool → Mem0 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 →