dotnet/aspnet-api-versioning

Provides a set of libraries which add service API versioning to ASP.NET Core Minimal APIs, Controllers, gRPC, OData, and Web API (Classic).

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on July 26th, 2016
Open Issues & Pull Requests: 11 (+0)
GitHub issues: Enabled
Number of forks: 721
Total Stargazers: 3,205 (+0)
Total Subscribers: 107 (+0)

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 13.2 days
90th percentile: 2.0 hours
Tracked items: 78

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 7, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 22 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • asp.net core (49)
  • bug (31)
  • answered (24)
  • question (18)
  • enhancement (16)
  • odata (12)
  • triage (12)
  • external (5)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

ASP.NET API Versioning is a set of libraries that add API versioning to ASP.NET Core Minimal APIs, Controllers, gRPC, OData, and classic Web API applications.

The tool addresses the challenge of managing multiple API versions in REST services by providing metadata attributes and conventions that describe which versions are implemented by your endpoints. Rather than requiring new routing concepts or changes to how you build services, it layers versioning semantics onto your existing ASP.NET implementation. The default configuration follows the Microsoft REST Guidelines versioning semantics, with customization points available for services that need different versioning approaches or are transitioning from unversioned APIs.

The project supports a broad range of ASP.NET flavors: ASP.NET Core Minimal APIs, ASP.NET Core MVC, ASP.NET Core gRPC, ASP.NET Core with OData, and classic Web API with and without OData. Beyond core versioning, it includes API explorer and OpenAPI documentation support for versioned APIs across these platforms, as well as client-side HTTP client libraries for creating version-aware API consumers. Choose this tool if you need to version existing or new REST services without restructuring your application architecture, or if you require OpenAPI documentation that accounts for multiple API versions.

The project maintains active engagement with contributors through documented contribution guidelines and discussion channels. Development activity shows consistent attention to the codebase with regular updates across multiple supported platforms and frameworks. The breadth of supported ASP.NET variants indicates ongoing effort to keep the tool compatible as the ecosystem evolves.