Skip to content

Put the five things other people vouch for at the top - #108

Merged
michal-wrzosek merged 1 commit into
mainfrom
worktree-readme-badges
Sep 21, 2026
Merged

michal-wrzosek merged 1 commit into
mainfrom
worktree-readme-badges

Conversation

@michal-wrzosek

Copy link
Copy Markdown
Contributor

The README opened with install commands, which asks a stranger to act before
giving them a reason to. This adds the reasons, in the one form a reader
discounts least: none of the five is our own claim about ourselves.

Badge Says Source
Build status CI on this repository GitHub Actions
Version on npm v0.1.17 npm
Downloads a month ~1,100 and rising npm
License GPL-3.0-or-later static, see below
Glama MCP server rated A Glama

The Glama one is the one worth having

It reads "MCP server rated A on Glama", and its own description records what
sits behind it: claimed by its maintainer, tool definitions rated A across
seventeen tools, maintenance rated A. That grade comes from a scan of the
codebase, a build of the server, and a run of it inside a sandbox where the
syscall and network layers were watched.

It is the only line in the row we could not have produced ourselves, and until
now it existed only on Glama's website, where nobody looking at this project
would see it.

Two small decisions

Five, not six. A GitHub release badge would show the same number as the npm
one. A row where two badges repeat each other teaches a reader to skip the row.

The license badge is static. Shields can read the license from GitHub, and
GitHub detects this project as GPL-3.0. The license is GPL-3.0-or-later,
and "or later" is the part with legal effect, so the badge spells it out rather
than being convenient.

All five endpoints were checked and return image/svg+xml with a 200. All five
render twenty pixels tall, so they sit on a single line.

🤖 Generated with Claude Code

A README that opens with install commands asks a stranger to act before it has
given them any reason to. These five lines are the reasons, and none of them is
our own claim about ourselves: a build somebody else ran, a version and a
download count somebody else counts, a licence, and a score from a directory
that read the code and ran the server in a sandbox.

The Glama one is the only one that is new and the only one that is hard to get.
It reads "MCP server rated A on Glama", and behind it sit a security scan of
the built image, seventeen tool definitions graded on six dimensions each, and
a maintenance grade. That is a third party saying the thing we cannot credibly
say about ourselves, and it was sitting on their website doing nothing for us.

Five and no more, all twenty pixels tall so they sit on one line. The GitHub
release badge was left out because it says the same number as the npm one, and
a row where two badges repeat each other teaches a reader to skip the row.

The licence badge is static rather than read from the repository. GitHub
detects this project as GPL-3.0 and the badge would say so, but the licence is
GPL-3.0-or-later and the "or later" is the part with legal effect.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@michal-wrzosek
michal-wrzosek merged commit c822365 into main Sep 21, 2026
5 checks passed
@michal-wrzosek
michal-wrzosek deleted the worktree-readme-badges branch September 21, 2026 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant