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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed today
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
57.7k
Forks
6.6k
Last Push
2026-06-04
today
Commits (4 wk)
59
Downloads (7d)
767,327
pypi
HN mentions (30d)
513
Open Issues
419
Rank Change
▼2
was #20
Analysis
HVTrust Dimensions
88.0 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
18.8 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
12.8 / 17
MaintenanceFreshness and commits
19.1 / 20
AdoptionStars and downloads
19.3 / 20
Activity Inputs
93.6 / 100
StarsRepository reach
28.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.2 / 25
CommunityFork signal
17.8 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.0 / 10
via deps.dev · OpenSSF
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-Policy0
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.0/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.
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
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.
