Is Claude Mem safe to use?

Claude Mem has an HVTrust score of 76.6/100 (Grade B), ranked #23 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Claude Mem?

Claude Mem scores 76.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 94.7k GitHub stars and is categorized under Agent Skills.

Claude Mem

thedotmack/claude-mem

Persistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More

Agent Skills TypeScript Listed Apache-2.0

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

OSSF Scorecard 4.5 / 10

Provenance None

Signed commits 98%

Last push today

Compare Claude Mem

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Claude Mem scores 76.6/100 (Grade B), ranked #23 of 351 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.5/10; 98% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Mem compares in Agent Skills

Bars show each HVTrust score; the tick marks Claude Mem’s 76.6.

Where the 76.6 comes from

HVTrust dimensions vs the Agent Skills average

76.6 / 100 · 100.0% confidence

Claude Mem Agent Skills average (351 agents)

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

10.5 / 25

2.4 above avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

12.3 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.8 above avg 14.2

AdoptionLog-scaled stars · package downloads

17.3 / 20

8.3 above avg 9.0

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.5/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 Claude Mem View Agent Skills Report missing data

98.1

Activity sub-score · out of 100

#23

In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

94.7k

Forks

8.4k

Last Push

2026-09-26

today

Commits (4 wk)

273

Downloads (7d)

10,759

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #23

Analysis

Activity Inputs

98.1 / 100

StarsRepository reach

29.9 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

18.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.5 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

98%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 8

CII-Best-Practices 0

Code-Review 3

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

Common questions about Claude Mem

Public supply-chain signals for Claude Mem are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Claude Mem carries less obvious unverified-evidence risk than projects with thin signals.

Does Claude Mem publish package provenance?

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

Does Claude Mem have an OpenSSF Scorecard?

Claude Mem has an OpenSSF Scorecard score of 4.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 Claude Mem actively maintained?

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

What license does Claude Mem use?

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

Are Claude Mem's commits signed?

98% of the last 100 commits to Claude Mem 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

Claude Mem appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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 Claude Mem'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-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Claude Mem?

For maintainers

HVTrust scores Claude Mem 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-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 179 spots (#206 → #27)

2026-09-23

HVTrust Changed

HVTrust up 40.2pts (34.7 → 74.9)

2026-09-22

Newly Listed

First tracked at rank #206

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-02

Scorecard Added

OSSF Scorecard: 4.3/10

2026-09-02

Grade Changed

Trust grade D → B

2026-09-02

Rank Moved

Rank rose 167 spots (#180 → #13)

2026-09-02

HVTrust Changed

HVTrust up 28.7pts (45.0 → 73.7)

2026-09-01

Rank Moved

Rank dropped 14 spots (#166 → #180)

2026-08-31

Rank Moved

Rank dropped 18 spots (#148 → #166)

2026-08-30

Rank Moved

Rank dropped 28 spots (#120 → #148)

2026-08-29

Rank Moved

Rank dropped 27 spots (#93 → #120)

2026-08-28

Rank Moved

Rank dropped 21 spots (#72 → #93)

2026-08-27

Rank Moved

Rank dropped 20 spots (#52 → #72)

2026-08-26

Rank Moved

Rank dropped 40 spots (#12 → #52)

2026-08-22

Activity Score Changed

Activity score down 8pts (98 → 90)

2026-08-11

Newly Listed

First tracked at rank #10

GitHub → npm: claude-mem

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Skills

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