Is Memsearch safe to use?

Memsearch has an HVTrust score of 39.3/100 (Grade D), ranked #16 of 148 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Memsearch?

Memsearch scores 39.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.5k GitHub stars and is categorized under Agent Skills.

Memsearch

zilliztech/memsearch

A persistent, unified memory layer for all your AI agents (e.g. Claude Code, Codex), backed by Markdown and Milvus.

Agent Skills Python Grade D Listed MIT

39.3/100

Rank #16 of 148

Compare Memsearch

How does it stack up against its Agent Skills 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-31 · 12d ago

Recent change

New

Is Memsearch safe? Memsearch scores 39.3/100 (Grade D), ranked #16 of 148 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 85% of recent commits are signed; last pushed 2026-07-31. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#14 Context Mode — 41.5 (D) → #15 Superpowers Zh — 40.9 (D) → #17 Lobehub — 38.4 (D) → #18 Skill Seekers — 37.8 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-11

Newly Listed

First tracked at rank #16

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Compare with another agent Get email alerts for Memsearch View Agent Skills Report missing data

72.1

Activity sub-score · out of 100

#16

In Agent Skills

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 →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

2.5k

Forks

224

Last Push

2026-07-31

12 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #16

Analysis

HVTrust Dimensions vs Agent Skills

39.3 / 100 · 67.0% confidence

Memsearch Agent Skills average (148 agents)

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

11.8 / 25

9.1 above avg 2.7

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.7 above avg 11.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.5

Maintenance60% last-push freshness · 40% commit activity

16.8 / 20

1.7 above avg 15.1

AdoptionLog-scaled stars · package downloads

8.1 / 20

1.1 below avg 9.2

Activity Inputs

72.1 / 100

StarsRepository reach

20.3 / 30

FreshnessLast push recency

23.3 / 25

ActivityRecent commits

17.4 / 25

CommunityFork signal

10.9 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

—

Not available

Signed Commits

85%

of last 100 commits verified

Is Memsearch safe?

Public trust evidence for Memsearch 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 Memsearch publish package provenance?

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

Does Memsearch have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Memsearch. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Memsearch actively maintained?

Maintained. Last push was 12 days ago.

What license does Memsearch use?

Memsearch ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Memsearch's commits signed?

85% of the last 100 commits to Memsearch 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

4 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

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Memsearch?

For maintainers

HVTrust scores Memsearch 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-08-11

Newly Listed

First tracked at rank #16

GitHub → PyPI: memsearch

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Skills

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