updated 2026-08-09 19:31 UTC

Memvid

memvid/memvid

Memory layer for AI Agents. Replace complex RAG pipelines with a serverless, single-file memory layer. Give your agents

Memory & Knowledge Rust Grade D Listed Apache-2.0
49.2/100
Rank #450 of 1204
Compare Memvid

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-14 · 26d ago
Recent change
Rank +3

Is Memvid safe? Memvid scores 49.2/100 (Grade D), ranked #450 of 1204 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.7/10; 37% of recent commits are signed; last pushed 2026-07-14. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#30 LLM Wiki Agent — 51.1 (C) → #31 LightMem — 50.2 (C) → #33 LycheeMemory — 48.1 (D) → #34 ByteRover CLI — 47.3 (D) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 111 spots (#332 → #443)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-07
Scorecard Added
OSSF Scorecard: 3.7/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Memvid View Memory & Knowledge Report missing data
67.3
Activity sub-score · out of 100
#32
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-09 19:31 UTC · Repo last pushed 26 days ago

Activity & Reach

Stars
16.2k
Forks
1.4k
Last Push
2026-07-14
26 days ago
Commits (4 wk)
2?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
13
Rank Change
▼7
was #443

Analysis

HVTrust Dimensions vs Memory & Knowledge

49.2 / 100 · 100.0% confidence

Memvid Memory & Knowledge average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.5 / 25
4.1 below avg 10.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.5 below avg 12.3
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
1.1 below avg 12.7
Maintenance60% last-push freshness · 40% commit activity
11.2 / 20
6.3 below avg 17.5
AdoptionLog-scaled stars · package downloads
10.1 / 20
4.0 below avg 14.1

Activity Inputs

67.3 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
21.4 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
14.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.7 / 10
OpenSSF Scorecard · scanned Aug 9, 2026
Signed Commits
37%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 8
Packaging -1
Pinned-Dependencies 2
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Memvid safe?

Public trust evidence for Memvid is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Memvid publish package provenance?
No published build provenance is currently detected for Memvid. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Memvid have an OpenSSF Scorecard?
Memvid has an OpenSSF Scorecard score of 3.7/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 Memvid actively maintained?
Maintained. Last push was 26 days ago.
What license does Memvid use?
Memvid ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Memvid's commits signed?
37% of the last 100 commits to Memvid 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 Memvid'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-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain Memvid?

For maintainers

HVTrust scores Memvid 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
Rank 4Listed 1Scorecard 1Surface 1
2026-08-08
Rank Moved
Rank dropped 111 spots (#332 → #443)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-07
Scorecard Added
OSSF Scorecard: 3.7/10
2026-08-03
Rank Moved
Rank dropped 14 spots (#435 → #449)
2026-07-28
Rank Moved
Rank dropped 17 spots (#414 → #431)
2026-07-14
Rank Moved
Rank dropped 43 spots (#367 → #410)
2026-07-13
Newly Listed
First tracked at rank #367
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 49.2 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/memvid.svg)](https://hvtracker.net/agents/memvid)
HTML:
<a href="https://hvtracker.net/agents/memvid"><img src="https://hvtracker.net/badge/memvid.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

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