Best Open-Source Memory & Knowledge: OpenViking vs ReMe
A data-backed comparison of the top two memory & knowledge on HVTracker, built from public trust signals rather than stars alone.
Short answer: OpenViking currently leads ReMe on HVTracker's evidence-weighted trust score: 88.3 vs 87.8/100. This is not a popularity ranking; it combines supply-chain safety, identity/provenance, transparency, maintenance, and adoption signals.
OpenViking
Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.
ReMe
ReMe: Memory Management Kit for Agents - Remember Me, Refine Me.
OpenViking vs ReMe: trust signal breakdown
Both projects are tracked in the Memory & Knowledge category, but they do not expose the same evidence. The table below compares the public signals that feed HVTrust.
| Signal | OpenViking | ReMe |
|---|---|---|
| HVTrust score | 88.3 | 87.8 |
| Safety / Integrity | 20.5/25 | 20.5/25 |
| Identity / Provenance | 18.0/18 | 18.0/18 |
| Transparency | 13.9/17 | 13.9/17 |
| Maintenance | 20.0/20 | 18.8/20 |
| Adoption | 17.8/20 | 13.9/20 |
| OSSF Scorecard | 6.4 | 6.4 |
| Signed commits | 100% | 100% |
| Package provenance | Verified | Verified |
Which one should you evaluate first?
If your priority is the most verifiable trust profile today, start with OpenViking. It has the stronger current HVTrust score and ranks higher in Memory & Knowledge. If your use case depends on a specific runtime, language, license, or integration model, use the individual profiles rather than the headline score alone.
For production use, the practical checklist is: inspect the security policy, confirm package provenance or release signing where available, review recent maintenance cadence, and compare the exact trust breakdown. HVTracker is meant to reduce the first-pass research burden, not replace your own risk review.