Release Badges

ReleaseRun Badges for .NET

Live version freshness, EOL status, CVE counts, and health badges for .NET. Embed in your README, docs, or dashboard.

Live Badges

.NET Health Loading latest version badges...

Why Use .NET Health Badges?

.NET’s alternating LTS/STS release model creates a support matrix most teams can’t keep straight. A health badge in your project README shows whether your .NET version is still receiving security patches — no need to cross-reference Microsoft’s lifecycle pages.

ReleaseRun badges go beyond Shields.io. Where Shields.io displays a 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

  • NuGet package maintainers: Show which .NET versions your package targets and flag when any of them drop out of support. .NET 7 going EOL caught a lot of STS adopters off guard.
  • Enterprise teams: Embed badges in Azure DevOps wikis or internal dashboards to track .NET versions across your service fleet. Knowing what’s running is step one of any upgrade plan.
  • Open-source projects: Add version health next to your TargetFramework requirements so contributors verify 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 documentation builds.

.NET Versions

Loading version data...

Security Overview

CVE vulnerability data is sourced from the NIST National Vulnerability Database (NVD) and refreshed every 6 hours.

.NET CVE Badge

Check specific version CVEs using the badge builder above or visit our .NET hub page for detailed security analysis.

Upgrade Guidance

Running an older version of .NET? 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 .NET documentation for detailed upgrade instructions.

Version Comparison

Not sure which .NET version to use? Compare versions side by side.

Loading comparison data...

Embed Builder

Usage Guide

Copy any snippet below to embed a .NET health badge in your project.

Markdown

[![.NET Health](https://img.releaserun.com/badge/health/dotnet.svg)](https://releaserun.com/dotnet/)

HTML

<a href="https://releaserun.com/dotnet/"><img src="https://img.releaserun.com/badge/health/dotnet.svg" alt=".NET Health"></a>

reStructuredText

.. image:: https://img.releaserun.com/badge/health/dotnet.svg
   :target: https://releaserun.com/dotnet/
   :alt: .NET Health
Data updated daily 00:00 UTC

Data sources: endoflife.date (version lifecycle), NIST NVD (CVE data)

Related Articles

Kubernetes Gateway API vs Ingress: A 2025 Decision Framework That Won’t Surprise You in Prod

Last Updated: 2026-01-02 Kubernetes Gateway API vs Ingress: A 2025 Decision Framework That Won’t Surprise You in Prod Quick Navigation…

Frequently Asked Questions

What do the badges show for .NET?
ReleaseRun badges display real-time version freshness, end-of-life status, CVE vulnerability counts, and an overall health score for .NET releases.
How do I embed a .NET 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 .NET 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.