MemOS
Self-evolving memory OS for LLM & AI Agents: ultra-persistent memory, hybrid-retrieval, and cross-task skill reuse, with 35.24% token savings and DeepSeek Harness support.
Is MemOS safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare MemOS
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →In detail: MemOS scores 52.6/100 (Grade C), ranked #936 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 33% of recent commits are signed; last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →
How MemOS 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.0 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, Fuzzing 0 +8.3 → 60.9 C · #36 of 51
- Sign every commit33% signed today +3.3 → 55.9 C · #42 of 51
Chain of custody
Scanners check what the code says. This traces who ships MemOS and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/MemTensor/MemOS, Apache-2.0, last pushed 2026-10-17. 33% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.0/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:
- Code Review9
- Branch Protection5
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 5CI-Tests 10CII-Best-Practices 0Code-Review 9Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 2SAST 0Security-Policy 0Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. MemOS is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of MemOS.
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues MemOS’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.
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 MemOS compares in Memory & Knowledge
- #42 Memmy 54.9 +2.3
- #43 pgvector 53.1 +0.5
- #44 MemOS 52.6 this agent
- #45 inno-agent 50.7 −1.9
- #46 LLM Wiki Agent 47.9 −4.7
Bars show each HVTrust score; the tick marks MemOS’s 52.6.
Where the 52.6 comes from
HVTrust dimensions vs the Memory & Knowledge average
52.6 / 100 · 100.0% confidenceMemOS Memory & Knowledge average (51 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
76.3 / 100Common questions about MemOS
Does MemOS publish package provenance?
Does MemOS have an OpenSSF Scorecard?
Is MemOS actively maintained?
What license does MemOS use?
Are MemOS's commits signed?
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.
AI agent surface
MCP, providers, tool surface
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 →
- browser
- database
- search
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MemOS'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.
Maintain MemOS?
For maintainers
HVTrust scores MemOS 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/memos)
<a href="https://hvtracker.net/agents/memos"><img src="https://hvtracker.net/badge/memos.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON