updated 2026-08-19 05:02 UTC

ReMe

agentscope-ai/ReMe

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

Memory & Knowledge Python Grade B Listed Apache-2.0
75.3/100
Rank #92 of 1308
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-08-19 · 0d ago
Recent change
Tool Surface Changed

Is ReMe safe? ReMe scores 75.3/100 (Grade B), ranked #92 of 1308 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 5.6/10; 100% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#5 LightRAG — 84.1 (A) → #6 Hindsight — 83.1 (A) → #8 FAISS — 74.9 (B) → #9 Weaviate — 74.7 (B) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/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 Vespa Get email alerts for ReMe View Memory & Knowledge Report missing data
79.7
Activity sub-score · out of 100
#7
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 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 →

Signals refreshed 2026-08-19 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
3.3k
Forks
287
Last Push
2026-08-19
today
Commits (4 wk)
59
Downloads (7d)
412,202
pypi
HN mentions (30d)
—
Open Issues
17
Rank Change
▼5
was #87

Analysis

HVTrust Dimensions vs Memory & Knowledge

75.3 / 100 · 100.0% confidence

ReMe Memory & Knowledge average (44 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.0 / 25
2.1 above avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
0.9 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
19.1 / 20
1.4 above avg 17.7
AdoptionLog-scaled stars · package downloads
15.9 / 20
2.3 above avg 13.6

Activity Inputs

79.7 / 100
StarsRepository reach
21.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.2 / 25
CommunityFork signal
11.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.6 / 10
OpenSSF Scorecard · scanned Aug 17, 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 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 2
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 8

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?
No published build provenance is currently detected for ReMe. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does ReMe have an OpenSSF Scorecard?
ReMe has an OpenSSF Scorecard score of 5.6/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 Vespa → ReMe vs LanceDB → ReMe vs Mem0 →

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-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
Listed 1HVTrust 1Rank 1Grade 1Scorecard 1Surface 1
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
HVTrust 75.3 Grade B
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