Is Mem0 safe?
Mem0 scores 86.1/100 (Grade A), ranked #23 of 328 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-07-10. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Strong public trust posture, backed by multiple independent signals.
86.1/100 · Grade A
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
19.4/25
What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
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 →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed yesterday
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
60.6k
Forks
7.0k
Last Push
2026-07-10
yesterday
Commits (4 wk)
227
Downloads (7d)
812,269
npm+pypi
HN mentions (30d)
553
Open Issues
156
Rank Change
▼1
was #22
Analysis
HVTrust Dimensions
86.1 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
19.4 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
13.2 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
19.4 / 20
Activity Inputs
96.6 / 100
StarsRepository reach
28.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.9 / 20
Supply Chain Trust
Package Provenance
Verified
npm, pypi attestation
OSSF Scorecard
5.5 / 10
OpenSSF Scorecard · scanned Jul 3, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies0
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
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.
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.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
code
database
search
shell
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.
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Google Gemini, OpenAI, Pinecone, Postgres, Qdrant, Redis, Supabase, Weaviate
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-05-24
Provenance Added
Package provenance attestation detected
Maintain Mem0?
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.
