Skip to content

docs: surface open source presence in README header#46

Merged
liam-machine merged 1 commit into
mainfrom
docs/readme-open-source-badges
May 25, 2026
Merged

docs: surface open source presence in README header#46
liam-machine merged 1 commit into
mainfrom
docs/readme-open-source-badges

Conversation

@liam-machine

Copy link
Copy Markdown
Owner

Adds the canonical GitHub "this is open source" signals to the README header without making the page shouty about it.

Changes

  • GitHub stars badge in the existing badge row, linking to the repo. Styled flat + VS Code blue (#0078d4) to match the marketplace badges already there.
  • MIT license badge → clickable link to LICENSE (was a static image).
  • Small italic sub-line under the badge row: "Free and open source — built in the open on GitHub. Issues, PRs, and stars welcome."

Body copy on line ~36 ("free and open source alternative") and footer mention are left as-is — each says it a different way.

Why

The README already said "open source" three times, but none of them were the top-of-fold signal readers scan for. The badge row was marketplace-only; nothing hinted at the GitHub presence until you reached the footer.

🤖 Generated with Claude Code

Add a GitHub stars badge to the existing badge row and a short italic
sub-line under it inviting issues/PRs/stars. Make the MIT license badge
clickable (links to LICENSE).

The body and footer already mentioned open source, but neither the
header badges nor the visual top-of-fold signaled "this is on GitHub,
read/star the source." Stars badge matches marketplace badge style
(flat, VS Code blue) so the row stays visually coherent.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@liam-machine liam-machine merged commit 9f8e985 into main May 25, 2026
2 checks passed
@liam-machine liam-machine deleted the docs/readme-open-source-badges branch May 25, 2026 04:11
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