Is MemOS safe to use?

MemOS has an HVTrust score of 59.2/100 (Grade C), ranked #326 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MemOS?

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

MemOS

MemTensor/MemOS

Self-evolving memory OS for LLM & AI Agents: ultra-persistent memory, hybrid-retrieval, and cross-task skill reuse, with

Memory & Knowledge TypeScript Grade C Listed Apache-2.0

59.2/100

Rank #326 of 1204

Compare MemOS

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-07 · 2d ago

Recent change

Rank +1

Is MemOS safe? MemOS scores 59.2/100 (Grade C), ranked #326 of 1204 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 4.8/10; 85% of recent commits are signed; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#24 memU — 61.4 (C) → #25 PrivateGPT — 59.9 (C) → #27 pgvector — 58.5 (C) → #28 OpenViking — 55.7 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 102 spots (#224 → #326)

2026-08-08

Activity Score Changed

Activity score down 6pts (85 → 79)

2026-07-14

Scorecard Added

OSSF Scorecard: 4.6/10

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for MemOS View Memory & Knowledge Report missing data

79.0

Activity sub-score · out of 100

#26

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 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 →

Activity & Reach

Stars

10.7k

Forks

987

Last Push

2026-08-07

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #326

Analysis

HVTrust Dimensions vs Memory & Knowledge

59.2 / 100 · 100.0% confidence

MemOS Memory & Knowledge average (38 agents)

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

10.2 / 25

in line with avg 10.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.5 below avg 12.3

Transparency50% declared license · 50% OSSF Scorecard

12.6 / 17

in line with avg 12.7

Maintenance60% last-push freshness · 40% commit activity

17.1 / 20

in line with avg 17.5

AdoptionLog-scaled stars · package downloads

9.7 / 20

4.4 below avg 14.1

Activity Inputs

79.0 / 100

StarsRepository reach

24.2 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

16.2 / 25

CommunityFork signal

13.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.8 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

85%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 9

CII-Best-Practices 0

Code-Review 6

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is MemOS safe?

MemOS has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MemOS publish package provenance?

No published build provenance is currently detected for MemOS. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MemOS have an OpenSSF Scorecard?

MemOS has an OpenSSF Scorecard score of 4.8/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 MemOS actively maintained?

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

What license does MemOS use?

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

Are MemOS's commits signed?

85% of the last 100 commits to MemOS 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.

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

MemOS appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

5 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

browser
database
search

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-08

Rank Moved

Rank dropped 102 spots (#224 → #326)

2026-08-08

Activity Score Changed

Activity score down 6pts (85 → 79)

2026-07-14

Scorecard Added

OSSF Scorecard: 4.6/10

2026-07-14

Grade Changed

Trust grade D → C

2026-07-14

Rank Moved

Rank rose 173 spots (#358 → #185)

2026-07-14

HVTrust Changed

HVTrust up 36.4pts (25.2 → 61.6)

2026-07-13

Newly Listed

First tracked at rank #358

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON