ReleaseRun Badges for Java
Live version freshness, EOL status, CVE counts, and health badges for Java. Embed in your README, docs, or dashboard.
Live Badges
Loading latest version badges...
Why Use Java Health Badges?
Java’s LTS-vs-feature release split means teams often don’t know if their JDK is still getting CVE patches. A health badge in your project README cuts through the Oracle-vs-OpenJDK-vs-vendor confusion and shows whether your Java version is still supported — at a glance.
ReleaseRun badges go beyond Shields.io. While Shields.io shows a version number, our badges show security posture: CVE counts, EOL countdowns, and a composite health grade that factors in freshness (35%), security (35%), and support status (30%).
Common Use Cases
- Library maintainers: Show which Java versions your library’s CI matrix covers and flag when any of them lose upstream support. Teams still on Java 11 need a nudge — its free support window is narrowing fast.
- Enterprise platform teams: Embed badges in internal wikis to track JDK versions across hundreds of microservices. Upgrade campaigns start with visibility.
- Spring Boot projects: Add version health next to your minimum Java requirements so contributors know they’re building against a supported runtime.
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 and any documentation build system.
Java 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 Java hub page for detailed security analysis.
Upgrade Guidance
Running an older version of Java? 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 Java documentation for detailed upgrade instructions.
Version Comparison
Not sure which Java version to use? Compare versions side by side.
Embed Builder
Usage Guide
Copy any snippet below to embed a Java health badge in your project.
Markdown
[](https://releaserun.com/eclipse-temurin/)HTML
<a href="https://releaserun.com/eclipse-temurin/"><img src="https://img.releaserun.com/badge/health/eclipse-temurin.svg" alt="Java Health"></a>reStructuredText
.. image:: https://img.releaserun.com/badge/health/eclipse-temurin.svg
:target: https://releaserun.com/eclipse-temurin/
:alt: Java HealthData sources: endoflife.date (version lifecycle), NIST NVD (CVE data)
Related Articles
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…
Node.js v25.5.0 Release Notes: --build-sea and Safer SQLite Defaults
Node.js v25.5.0 Release Notes: --build-sea and Safer SQLite Defaults I’ve watched “minor” Node upgrades break a Friday deploy. This one…
Chrome third-party cookies: what breaks, what to ship, how to test
Chrome third-party cookies: what breaks, what to ship, how to test Third-party cookies don’t fail all at once. They fail…
Frequently Asked Questions
- What do the badges show for Java?
- ReleaseRun badges display real-time version freshness, end-of-life status, CVE vulnerability counts, and an overall health score for Java releases.
- How do I embed a Java 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 Java 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.