docs: restore the Glama badge + add npm/CI/license badges to the README#67
Merged
Merged
Conversation
…ADME hero Bring back the Glama score badge alongside npm version, CI status, and Apache-2.0 license badges. Keep every badge on a single physical line so the row renders inline on both the GitHub repo page and the Marketplace listing for the polygraph-mcp-gate action — the Marketplace renderer turns each markdown line into its own block, so a multi-line badge list would stack vertically and break the listing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TZcTQCDwyFqdh59fPWDJAr
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.
What
Restores the Glama score badge and adds npm version, CI status, and Apache-2.0 license badges to the README hero, joining the existing graded-by-polygraph self-grade.
Final hero row (left→right):
npm·CI·license·Glama·graded by polygraph.Why one physical line
README.mdis rendered on two surfaces: the repo homepage and thepolygraph-mcp-gateMarketplace listing. An earlier change collapsed the badges to a single one because the Marketplace renderer stacks each markdown line as its own block, so a multi-line badge list rendered vertically and broke the listing.The fix is to keep every badge on one physical line, separated by spaces — they then flow inline (and wrap naturally) on both surfaces. A guard comment above the row documents this so it isn't re-split.
Badge choices
Trust-focused, and deliberately avoiding badges whose numbers could read as weak for a young project:
ci.yml), Apache-2.0 license, Glama (renders a greenA A B), graded-by-polygraph self-grade.74— a middling score) and an OpenSSF Scorecard badge/workflow (young repos tend to score low). The Glama and polygraph self-grade badges already carry the security/trust signal, and render strongly.Verification
200+ an SVG content-type; the Glama badge rendersA A B(green); the polygraph badge307→200image (camo follows the redirect).polygraph-mcp-gateaction and its pinnedversioninput are untouched.