Feature: optional HVTrust supply-chain badge for the README

[YugantM]

Summary

Add an optional HVTrust supply-chain trust badge to the README. (Filing as a feature suggestion — your repo has blank issues disabled and this fits the feature-request flow best; happy to move it to Discussions if you'd prefer.)

Context / motivation

I maintain HVTracker (hvtracker.net), an independent, open trust registry for AI agents and MCP servers. Projects are scored on public, verifiable signals only — release/package provenance and signed commits, OpenSSF Scorecard, download/maintenance evidence, and supply-chain checks — producing a transparent HVTrust score + letter grade. No pay-to-rank; the methodology is fully public.

Codebase Memory MCP is already listed:

HVTrust 90.4 · Grade A — ranked #8 of 417 tracked projects
Full evidence breakdown: https://hvtracker.net/agents/codebase-memory-mcp/

Proposed change

A one-line, auto-updating badge in the README (stays accurate as the score changes):

[![HVTrust](https://hvtracker.net/badge/codebase-memory-mcp.svg)](https://hvtracker.net/agents/codebase-memory-mcp/)

Letter-grade and 30-day-trend variants are available too: https://hvtracker.net/badge/codebase-memory-mcp-grade.svg / https://hvtracker.net/badge/codebase-memory-mcp-trend.svg.

If you think a signal is off, we correct on evidence — no account needed: https://hvtracker.net/correct/

No pressure at all — if this isn't useful, just close it and I won't follow up. Thanks for building Codebase Memory MCP! 🙏

[DeusData]

Thanks for the suggestion and for documenting the methodology. We keep the README trust surface limited to project-controlled release evidence and a small set of maintainer-selected ecosystem standards. We are not adding third-party ranking badges or auto-loaded external badge assets, so I am closing this as out of scope. The existing listing can remain your independent assessment, but it is not an integration we will endorse in the project README.