Mem0 has an HVTrust score of 86.1/100 (Grade A), ranked #73 of 1371 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.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 66.9k GitHub stars and is categorized under Memory & Knowledge.

Mem0

Repository Website

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

Memory & Knowledge Python Listed Apache-2.0

Is Mem0 safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.5 / 10

Provenance Attested

Signed commits 100%

Last push today

Advisories None known

Compare Mem0

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

Pick any agent to compare →

Suggest a correction

In detail: Mem0 scores 86.1/100 (Grade A), ranked #73 of 1371 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; no published advisory affects its latest release (mem0ai); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mem0 could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 5.5 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, Fuzzing 0 +5.9 → 92.0 A · #1 of 49

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Mem0 and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/mem0ai/mem0, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.5/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection5
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

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
Published packages Partly attested
- npm mem0ai Source link points back to this repo Build provenance attested
- PyPI mem0ai Source link isn't a GitHub repo Build provenance attested
What you install today No known advisories

Latest release checked: mem0ai 3.3.1. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Mem0.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions

Verify this score yourself

Every build re-issues Mem0’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Mem0 compares in Memory & Knowledge

Bars show each HVTrust score; the tick marks Mem0’s 86.1.

Where the 86.1 comes from

HVTrust dimensions vs the Memory & Knowledge average

86.1 / 100 · 100.0% confidence

Mem0 Memory & Knowledge average (49 agents)

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

19.4 / 25

8.1 above avg 11.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.4 above avg 12.6

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

0.6 above avg 12.6

Maintenance60% last-push freshness · 40% commit activity

18.7 / 20

1.3 above avg 17.4

AdoptionLog-scaled stars · package downloads

19.1 / 20

5.9 above avg 13.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Rank Moved

Rank dropped 24 spots (#46 → #70)

2026-09-21

Rank Moved

Rank rose 20 spots (#66 → #46)

Maintainer Checklist

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

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

93.1

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-09-29 2026-10-09

Activity & Reach

Stars

66.9k

Forks

7.9k

Last Push

2026-10-09

today

Commits (4 wk)

Downloads (7d)

471,085

pypi

HN mentions (30d)

488

Open Issues

374

Rank Change

▼1

was #72

Analysis

Activity Inputs

93.1 / 100

StarsRepository reach

29.0 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

21.0 / 25

CommunityFork signal

18.1 / 20

Common questions about Mem0

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 ReMe → Mem0 vs OpenViking → Mem0 vs LanceDB →

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

high confidence

Implemented

Mem0 appears to expose MCP server capabilities.

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

How this surface has changed

Detected changes to Mem0's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-03

Mcp Status Changed

Detected MCP server support changed: declared → implemented

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-09-23

Rank Moved

Rank dropped 24 spots (#46 → #70)

2026-09-21

Rank Moved

Rank rose 20 spots (#66 → #46)

2026-09-05

Rank Moved

Rank dropped 14 spots (#46 → #60)

2026-09-03

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-09-03

Rank Moved

Rank rose 11 spots (#51 → #40)

GitHub → Website → 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.4 · Raw JSON

Mem0

How Mem0 could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Partly attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Mem0 compares in Memory & Knowledge

Where the 86.1 comes from

HVTrust dimensions vs the Memory & Knowledge average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Mem0

Compare Mem0 head-to-head

AI agent surface

Maintain Mem0?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Memory & Knowledge