ReMe has an HVTrust score of 89.7/100 (Grade A), ranked #14 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for ReMe?

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

ReMe

agentscope-ai/ReMe

ReMe: Memory Management Kit for Agents - Remember Me, Refine Me.

Memory & Knowledge Python Grade A Listed Apache-2.0

89.7/100

Rank #14 of 1328

Compare ReMe

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

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-11 · 1d ago

Recent change

Provider Removed

Is ReMe safe? ReMe scores 89.7/100 (Grade A), ranked #14 of 1328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.1/10; 100% of recent commits are signed; last pushed 2026-09-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#2 OpenViking — 88.1 (A) → #3 Mem0 — 86.1 (A) → #4 Vespa — 86.0 (A) → #5 Graphiti — 86.0 (A) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-12

Provider Removed

Runtime surface shrank — no longer detected: DeepSeek

2026-08-27

Provider Added

Runtime surface grew — new detected provider dependency: DeepSeek

2026-08-27

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with OpenViking Get email alerts for ReMe View Memory & Knowledge Report missing data

79.9

Activity sub-score · out of 100

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 A 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-12

Activity & Reach

Stars

3.4k

Forks

297

Last Push

2026-09-11

yesterday

Commits (4 wk)

Downloads (7d)

64,429

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲6

was #20

Analysis

HVTrust Dimensions vs Memory & Knowledge

89.7 / 100 · 100.0% confidence

ReMe Memory & Knowledge average (44 agents)

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

21.4 / 25

9.9 above avg 11.5

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.6 above avg 12.4

Transparency50% declared license · 50% OSSF Scorecard

14.5 / 17

1.6 above avg 12.9

Maintenance60% last-push freshness · 40% commit activity

19.0 / 20

1.6 above avg 17.4

AdoptionLog-scaled stars · package downloads

14.9 / 20

1.2 above avg 13.7

Activity Inputs

79.9 / 100

StarsRepository reach

21.2 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

22.2 / 25

CommunityFork signal

11.5 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

7.1 / 10

OpenSSF Scorecard · scanned Sep 8, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 10

CII-Best-Practices 0

Code-Review 9

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 5

SAST 10

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Is ReMe safe?

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

Does ReMe publish package provenance?

Yes. ReMe's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does ReMe have an OpenSSF Scorecard?

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

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

What license does ReMe use?

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

Are ReMe's commits signed?

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

Compare ReMe head-to-head

ReMe vs OpenViking → ReMe vs Mem0 → ReMe vs Vespa →

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

ReMe appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

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 ReMe'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-12

Provider Removed

Runtime surface shrank — no longer detected: DeepSeek

2026-08-27

Provider Added

Runtime surface grew — new detected provider dependency: DeepSeek

2026-08-27

Provenance Added

Package provenance attestation detected

2026-08-22

Provider Removed

Runtime surface shrank — no longer detected: DeepSeek

2026-08-21

Provider Added

Runtime surface grew — new detected provider dependency: DeepSeek

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

Maintain ReMe?

For maintainers

HVTrust scores ReMe 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-12

Provider Removed

Runtime surface shrank — no longer detected: DeepSeek

2026-08-27

Provider Added

Runtime surface grew — new detected provider dependency: DeepSeek

2026-08-27

Provenance Added

Package provenance attestation detected

2026-08-27

Grade Changed

Trust grade B → A

2026-08-27

Rank Moved

Rank rose 73 spots (#96 → #23)

2026-08-27

HVTrust Changed

HVTrust up 12.1pts (76.4 → 88.5)

2026-08-22

Provider Removed

Runtime surface shrank — no longer detected: DeepSeek

2026-08-22

Rank Moved

Rank rose 14 spots (#95 → #81)

2026-08-21

Provider Added

Runtime surface grew — new detected provider dependency: DeepSeek

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-07-29

Scorecard Added

OSSF Scorecard: 5.6/10

2026-07-29

Grade Changed

Trust grade D → B

2026-07-29

Rank Moved

Rank rose 265 spots (#353 → #88)

2026-07-29

HVTrust Changed

HVTrust up 31.2pts (42.5 → 73.7)

2026-07-28

Newly Listed

First tracked at rank #353

GitHub → PyPI: reme-ai

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Memory & Knowledge

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