Make the README findable - #2
Merged
Merged
Conversation
The prose was already right; what was missing was everything that makes a repo discoverable. Adds badges, the project mark, and keyword-bearing opening lines so the summary that appears in search results says "self-hosted secrets manager" rather than an elegant phrase nobody types into a search box. Adds a comparison table against Vault, OpenBao, Infisical and plain .env files. It concedes the two rows where those tools win outright — high availability and dynamic secrets — because a comparison that claims to win everywhere reads as marketing and gets discounted entirely. Names the audience explicitly, including the specific moment that makes someone need this: noticing your API keys sit in plaintext in an MCP client config. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The prose was already right. What was missing was everything that makes a repo discoverable.
Topics were empty — the single biggest discovery gap on GitHub. Now 18, covering
secrets-management,mcp,ai-agents,vault-alternative,self-hosted.Opening lines carry keywords. "Encrypted secret storage with one core and three surfaces" is elegant but nobody types it into a search box. Now leads with "self-hosted secrets manager", and names the moment that makes someone need this: noticing your API keys sit in plaintext in an MCP client config.
Comparison table against Vault, OpenBao, Infisical and plain
.envfiles. It concedes the rows where those tools win outright — HA, dynamic secrets, PKI, SSO. A table that wins everywhere reads as marketing and gets discounted entirely; the two rows without a real competitor (MCP server, agent policy enforcement) land harder for being surrounded by honest losses.Badges and the project mark for at-a-glance credibility.
No prose was rewritten and no claims were added.
🤖 Generated with Claude Code