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 releases new versions every six months, and only the latest two minor versions receive security patches. A health badge in your README gives instant visibility into whether a 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%).
Go Release History & EOL Timeline
The Go team releases a new minor version roughly every six months (February and August). Each minor version is supported until two newer minor versions exist — meaning only the latest two releases receive patches at any time. This aggressive support window makes Go one of the fastest-moving runtimes to track.
- Go 1.24 — released February 2025. Current stable. Actively receiving patches.
- Go 1.23 — released August 2024. Still receiving security patches (second-latest). Will reach EOL when Go 1.25 ships (~August 2025).
- Go 1.22 — released February 2024. End-of-life since February 2025 (superseded by 1.23 and 1.24). No more security patches.
- Go 1.21 and earlier — end-of-life. Known CVEs remain unpatched. The ReleaseRun badge grade drops to F.
Go’s two-version support policy means the window between “current” and “unsupported” is only 12 months. Health badges make this visible — when your version drops out of the supported pair, the badge turns red immediately.
Badge Customization Examples
Four badge types are available for Go:
- Health badge — composite A–F grade. Embed:
 - Freshness badge — how current your version is. Embed:
 - EOL badge — end-of-life status. Embed:
 - CVE badge — vulnerability count. Embed:
Customise with ?style=flat-square or ?style=for-the-badge. The embed builder above lets you preview all options before copying.
Common Use Cases
- Module maintainers: Show which Go versions your module 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 are targeting a supported toolchain.
Related ReleaseRun Tools
Go badges are part of a broader Go ecosystem toolkit:
- Go Module Health Check — scan your
go.modfor outdated or EOL dependencies. - Tech Stack Health Scorecard — get a holistic health grade across your entire Go-based stack.
- Dependency EOL Scanner — scan your dependency files and flag anything approaching end-of-life.
- EOL Timeline Visualizer — see Go EOL dates alongside your other dependencies on an interactive timeline.
- Upgrade Path Planner — plan your Go version upgrade with step-by-step guidance.
- CVE Dashboard — monitor known vulnerabilities across Go and all your other tracked products.
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
CI/CD Pipelines with Kubernetes: Best Practices and Tools
If you're studying DevOps or software engineering, you've probably heard that Kubernetes is "the standard" for running applications in production.…
Container-Optimized Linux Distributions Compared: Flatcar, Bottlerocket, Talos, and Fedora CoreOS
The moment your team starts running Kubernetes at scale, you start questioning whether a general-purpose Linux distribution is the right…
Node.js meta commits in v24.13.1: use meta: add
Node.js meta commits in v24.13.1: use meta: add Test first. Treat meta: add as release hygiene, not style. Should you…
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.