RegistryCompare › OpenViking vs ReMe

OpenViking vs ReMe

An independent, evidence-based trust comparison of OpenViking and ReMe, two Memory & Knowledge projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

ReMe leads on trust — 88.5/100 (Grade A) vs 87.9/100 (Grade A), a 0.6-point gap. Full breakdown below.
Signal OpenVikingvolcengine/OpenViking ReMeagentscope-ai/ReMe
HVTrust score 87.9 88.5
Evidence grade A A
Coverage grade B B
Overall rank #24 #21
Rank in Memory & Knowledge #2 #1
GitHub stars 35.3k 3.4k
Last updated today today
Build provenance Yes Yes
OSSF Scorecard 6.3 / 10 6.3 / 10
License AGPL-3.0 Apache-2.0
Downloads 80k/wk 84k/wk
Trust dimensions (points earned)
Safety / integrity / 25 20.4 20.4
Identity & provenance / 18 18.0 18.0
Transparency / 17 13.9 13.9
Maintenance / 20 20.0 19.6
Adoption / 20 17.5 15.0
Runtime capability surface (full matrix)
MCP server Declared Implemented
External providers 7 — Amazon Bedrock, Anthropic, Firecrawl, … 3 — Anthropic, DeepSeek, OpenAI
Requires API keys No Yes
Plugin surface plugins plugins
Provenance drift Match Match
Open in the live compare tool → OpenViking profile ReMe profile More Memory & Knowledge →

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →