Mem0 has an HVTrust score of 86.2/100 (Grade A), ranked #42 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Mem0?

Mem0 scores 86.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 64.0k GitHub stars and is categorized under Memory & Knowledge.

Mem0

mem0ai/mem0

Universal memory layer for AI Agents

Memory & Knowledge Python Grade A Listed Apache-2.0

86.2/100

Rank #42 of 1308

Compare Mem0

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-24 · 1d ago

Recent change

No recent signal change

Is Mem0 safe? Mem0 scores 86.2/100 (Grade A), ranked #42 of 1308 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 100% of recent commits are signed; last pushed 2026-08-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#1 Vespa — 87.8 (A) → #2 LanceDB — 86.8 (A) → #4 Graphiti — 85.7 (A) → #5 LightRAG — 84.0 (A) →

Quick Trust Read

What Would Improve It

Improve safety / integrity to lift the weakest part of the trust profile.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.

Compare with Vespa Get email alerts for Mem0 View Memory & Knowledge Report missing data

96.4

Activity sub-score · out of 100

In Memory & Knowledge

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

64.0k

Forks

7.5k

Last Push

2026-08-24

yesterday

Commits (4 wk)

Downloads (7d)

812,269

npm+pypi

HN mentions (30d)

553

Open Issues

254

Rank Change

▼4

was #38

Analysis

HVTrust Dimensions vs Memory & Knowledge

86.2 / 100 · 100.0% confidence

Mem0 Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

19.4 / 25

9.4 above avg 10.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.9 above avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

0.8 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

19.8 / 20

2.2 above avg 17.6

AdoptionLog-scaled stars · package downloads

19.4 / 20

5.8 above avg 13.6

Activity Inputs

96.4 / 100

StarsRepository reach

28.8 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

24.6 / 25

CommunityFork signal

18.0 / 20

Supply Chain Trust

Package Provenance

Verified

npm, pypi attestation

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Aug 24, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Mem0 safe?

Public supply-chain signals for Mem0 are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Mem0 carries less obvious unverified-evidence risk than projects with thin signals.

Does Mem0 publish package provenance?

Yes. Mem0's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Mem0 have an OpenSSF Scorecard?

Mem0 has an OpenSSF Scorecard score of 5.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Mem0 actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Mem0 use?

Mem0 ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Mem0's commits signed?

100% of the last 100 commits to Mem0 are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Mem0 head-to-head

Mem0 vs Vespa → Mem0 vs LanceDB → Mem0 vs Graphiti →

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

14 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

database

Detailed evidence is not shown in the public view.

Package Provenance Drift

medium confidence

Partial

Some package metadata matches; some source metadata is missing

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Mem0?

For maintainers

HVTrust scores Mem0 from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (75.9 → 85.9)

2026-05-28

Activity Score Changed

Activity score up 22pts (71 → 93)

GitHub → PyPI: mem0ai npm: mem0ai

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mem0.svg)](https://hvtracker.net/agents/mem0)
            
HTML:
            <a href="https://hvtracker.net/agents/mem0"><img src="https://hvtracker.net/badge/mem0.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON