updated 2026-10-11 08:08 UTC

Memsearch

Repository Website by zilliztech

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

Agent Skills Python Listed MIT

Is Memsearch safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.8 / 10
Provenance Attested
Signed commits 87%
Last push 2d ago
Advisories None known
Compare Memsearch

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Memsearch scores 74.4/100 (Grade B), ranked #26 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.8/10; 87% of recent commits are signed; no published advisory affects its latest release (memsearch); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Memsearch could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Memsearch and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Signed

    github.com/zilliztech/memsearch, MIT, last pushed 2026-10-09. 87% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.8/10 (scanned Sep 25, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 1
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 0

  3. Published packages Partly attested

    • PyPI memsearch Source link isn't a GitHub repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: memsearch 0.4.21. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-01 OSSF Scorecard: 4.9/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Memsearch’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Memsearch compares in Agent Skills

  1. #24 Code Review Graph 76.1 +1.7
  2. #25 Openmed 74.8 +0.4
  3. #26 Memsearch 74.4 this agent
  4. #27 Computer Use Linux 74.1 −0.3
  5. #28 Arcgentic 72.3 −2.1

Bars show each HVTrust score; the tick marks Memsearch’s 74.4.

Where the 74.4 comes from

HVTrust dimensions vs the Agent Skills average

74.4 / 100 · 100.0% confidence

Memsearch Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.9 / 25
10.1 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.6 above avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
0.5 above avg 12.1
Maintenance60% last-push freshness · 40% commit activity
16.2 / 20
2.1 above avg 14.1
AdoptionLog-scaled stars · package downloads
13.0 / 20
4.0 above avg 9.0

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, DeepSeek, Google Gemini, Mistral AI, OpenAI
2026-09-23
Provenance Added
Package provenance attestation detected
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent Get email alerts for Memsearch View Agent Skills Report missing data
70.3
Activity sub-score · out of 100
#26
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 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-10-11 08:08 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
2.7k
Forks
266
Last Push
2026-10-09
2 days ago
Commits (4 wk)
11
Downloads (7d)
3,423
pypi
HN mentions (30d)
—
Open Issues
50
Rank Change
=
was #26

Analysis

Activity Inputs

70.3 / 100
StarsRepository reach
20.6 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
13.5 / 25
CommunityFork signal
11.3 / 20

Common questions about Memsearch

Memsearch has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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?
Memsearch has an OpenSSF Scorecard score of 4.8/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 Memsearch actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
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?
87% 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
5 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
How this surface has changed

Detected changes to Memsearch'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-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, DeepSeek, Google Gemini, Mistral AI, OpenAI
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-03
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek

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
Rank 11HVTrust 3Listed 2Surface 2Grade 2Scorecard 1Delisted 1Provenance 1Surface 1
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, DeepSeek, Google Gemini, Mistral AI, OpenAI
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 239 spots (#265 → #26)
2026-09-23
HVTrust Changed
HVTrust up 43.9pts (31.1 → 75.0)
2026-09-22
Newly Listed
First tracked at rank #265
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-06
Grade Changed
Trust grade D → B
2026-09-06
Rank Moved
Rank rose 185 spots (#205 → #20)
2026-09-06
HVTrust Changed
HVTrust up 29.2pts (46.6 → 75.8)
2026-09-05
Rank Moved
Rank dropped 11 spots (#194 → #205)
2026-09-03
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek
2026-09-03
Rank Moved
Rank dropped 10 spots (#180 → #190)
2026-09-01
Scorecard Added
OSSF Scorecard: 4.9/10
2026-09-01
Rank Moved
Rank rose 26 spots (#197 → #171)
2026-09-01
HVTrust Changed
HVTrust up 6.8pts (40.1 → 46.9)
2026-08-31
Rank Moved
Rank dropped 17 spots (#180 → #197)
2026-08-30
Rank Moved
Rank dropped 32 spots (#148 → #180)
2026-08-29
Rank Moved
Rank dropped 36 spots (#112 → #148)
2026-08-28
Rank Moved
Rank dropped 24 spots (#88 → #112)
2026-08-27
Rank Moved
Rank dropped 21 spots (#67 → #88)
2026-08-26
Rank Moved
Rank dropped 48 spots (#19 → #67)
2026-08-11
Newly Listed
First tracked at rank #16
GitHub → Website → PyPI: memsearch

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 74.4 Grade B
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON