Ci
gh-action-badge: generate SVG badges hosted in your repo's wiki
A pair of GitHub Actions that produce coverage and fixed-color SVG badges, stored in the repository wiki — no third-party badge service required.
Every README I write ends up sprouting badges. Build status, lint status, version, coverage. Most of those are easy because they come for free from a service — Shields.io, Codecov, the GitHub Actions badge endpoint. The annoying one is always coverage, because it requires either a third-party service or a separate pipeline that publishes the number somewhere. So I built gh-action-badge to host the badge SVGs in the one place I always have available: the repo’s own wiki.
gobadger: SVG badges for private GitLab repositories
A small Go CLI that generates SVG badges as artifacts, designed for private GitLab projects where shields.io can't reach
You know the colourful little badges on the top of every README — coverage, build status, version, all of that? Most of them come from shields.io, which works beautifully when your repo is public. The moment your project is private and lives on a self-hosted GitLab, those services can’t reach in. gobadger is the tool I wrote to solve that.