Registry › Compare › Mem0 vs ReMe

Mem0 vs ReMe

ReMe leads on trust: 89.5/100 (Grade A) against 83.4/100 (Grade A), a 6.1-point gap. Mem0 leads on adoption and rests on broader evidence; ReMe leads on supply-chain integrity and maintenance. Note: ReMe's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types.

A Mem0 83.4

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

mem0ai/mem0 · #128 overall · #11 Memory & Knowledge · coverage A (4/5)

Choose Mem0 if adoption matters most.

+4.1Adoption: 741.6k weekly downloads against 106.4k
A vs BEvidence coverage: 4 of 5 independent signal types, against 3

A ReMe 89.5

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

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

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

+4.5Maintenance: last push 1d ago, against 9d ago
+1.3Safety / Integrity: OSSF Scorecard 6.6 against 5.5
+0.9Transparency: OSSF Scorecard 6.6 against 5.5

Where they differ

19.4

Safety / IntegrityReMe +1.3

20.7

13.2

TransparencyReMe +0.9

14.1

15.0

MaintenanceReMe +4.5

19.5

19.4

AdoptionMem0 +4.1

15.3

-1.6

Runtime calibrationReMe +3.5

+1.9

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	83.4	89.5
Evidence grade	A	A
Coverage grade	A	B
Overall rank	#128	#39
Rank in Memory & Knowledge	#11	#1
GitHub stars	69.0k	3.8k
Last updated	9d ago	1d ago
Build provenance	Yes	Yes
OSSF Scorecard	5.5 / 10	6.6 / 10
License	Apache-2.0	Apache-2.0
Downloads	742k/wk	106k/wk
Trust dimensions (points earned)
Safety / integrity / 25	19.4	20.7
Identity & provenance / 18	18.0	18.0
Transparency / 17	13.2	14.1
Maintenance / 20	15.0	19.5
Adoption / 20	19.4	15.3
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.4 →