ReleaseRun Badges for Go
Live version freshness, EOL status, CVE counts, and health badges for Go. Embed in your README, docs, or dashboard.
Live Badges
Loading latest version badges...
Why Use Go Health Badges?
Go’s fast release cadence means your users might be running a version with known CVEs and not realise it. A health badge in your README gives instant visibility into whether their Go version is still patched and supported.
ReleaseRun badges go beyond Shields.io. Where Shields.io shows a static version number, our badges show security posture: CVE counts, EOL countdowns, and a composite health grade based on freshness (35%), security (35%), and support status (30%).
Common Use Cases
- Module maintainers: Show which Go versions your module’s CI matrix covers and whether those versions are still receiving security patches. When a version drops out of support, the badge flips automatically.
- Platform teams: Embed badges in internal dashboards to track which Go versions are deployed across microservices. One glance beats grepping Dockerfiles.
- Documentation sites: Add version health next to
go installinstructions so developers know they’re targeting a supported toolchain.
What Makes These Different
Every badge pulls live data from the endoflife.date API and the NIST National Vulnerability Database. Data refreshes every 6 hours. Badges are edge-cached for 5 minutes — fast enough for CI pipelines, documentation sites, or release notes pages.
Go Versions
Security Overview
CVE vulnerability data is sourced from the NIST National Vulnerability Database (NVD) and refreshed every 6 hours.
Check specific version CVEs using the badge builder above or visit our Go hub page for detailed security analysis.
Upgrade Guidance
Running an older version of Go? Here's what to consider when planning your upgrade:
- Check breaking changes in release notes
- Review EOL dates for your current version
- Test in staging before production rollout
- Consider LTS versions for stability
See the official Go documentation for detailed upgrade instructions.
Version Comparison
Not sure which Go version to use? Compare versions side by side.
Embed Builder
Usage Guide
Copy any snippet below to embed a Go health badge in your project.
Markdown
[](https://releaserun.com/go/)HTML
<a href="https://releaserun.com/go/"><img src="https://img.releaserun.com/badge/health/go.svg" alt="Go Health"></a>reStructuredText
.. image:: https://img.releaserun.com/badge/health/go.svg
:target: https://releaserun.com/go/
:alt: Go HealthData sources: endoflife.date (version lifecycle), NIST NVD (CVE data)
Related Articles
CHIPS is the new superpower for embedded widgets!
CHIPS is the new superpower for embedded widgets! If your iframe widget “forgets” users in Chrome, you’re already living in…
How to Add Version Health Badges to Your Project
Your README shows a build status badge, a coverage badge, and maybe a license badge. None of them tell users…
VS Code 1.109.0 Release Notes: Claude Agents, Integrated Browser, and the Stuff People Actually Mention
VS Code 1.109.0 Release Notes: Claude Agents, Integrated Browser, and the Stuff People Actually Mention Reddit’s already arguing about this…
Frequently Asked Questions
- What do the badges show for Go?
- ReleaseRun badges display real-time version freshness, end-of-life status, CVE vulnerability counts, and an overall health score for Go releases.
- How do I embed a Go badge in my README?
- Use the embed builder above to select your version and badge type, then copy the generated Markdown or HTML snippet into your README.
- How often is Go badge data updated?
- Badge data refreshes every 6 hours from endoflife.date and NIST NVD. Badges are cached for 5 minutes at the CDN edge.
- Can I customize the badge style?
- Yes, append ?style=flat-square or ?style=for-the-badge to the badge URL. The embed builder lets you preview all available styles.