dotnet/yarp

A toolkit for developing high-performance HTTP reverse proxy applications.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 37 minutes ago
Added to GitGenius on September 6th, 2026
Created on March 5th, 2020
Open Issues & Pull Requests: 191 (+0)
GitHub issues: Enabled
Number of forks: 933
Total Stargazers: 9,611 (+0)
Total Subscribers: 270 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.9 hours
Mean response time: 23.0 days
90th percentile: 9.0 days
Tracked items: 153

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 81% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 4% of issues opened in the past year have been closed. Three people close 66% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 59
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 908 days
Stale 30+ days: 56
Stale 90+ days: 46

Recent activity

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

Top labels

  • Type: Bug (61)
  • Type: Idea (38)
  • needs-author-action (28)
  • Kubernetes Ingress Controller (9)
  • Type: Documentation (9)
  • help wanted (9)
  • Container (7)
  • External: AspNetCore (7)

Detailed Description

YARP is a toolkit for building high-performance HTTP reverse proxy applications in .NET.

YARP addresses the need for organizations to deploy reverse proxies tailored to their specific infrastructure and operational requirements. Rather than offering a monolithic proxy server, the project provides a library and extensible pipeline designed around customization as a primary use case. The toolkit leverages ASP.NET and .NET infrastructure to deliver performance while allowing developers to programmatically manage configuration, integrate with their own backend systems, and modify proxy behavior without rebuilding from source or resorting to scripting.

Teams should adopt YARP when they need a reverse proxy that can be deeply customized for their deployment scenario and integrated into a .NET ecosystem. The project suits organizations already invested in .NET who want to avoid the operational overhead of managing a separate proxy binary or the limitations of configuration-file-only approaches. YARP is particularly valuable for teams managing multiple services with varying proxy requirements, since the in-process customization model allows each deployment to adapt the proxy behavior to its own needs without forking the codebase.

The project maintains a structured release cadence with regular updates published through the releases page, and developers can access daily builds for early testing of unreleased features. Development activity shows consistent attention to build infrastructure and developer experience, with documented setup scripts for Windows, Linux, and macOS that automate SDK provisioning and environment configuration. The team actively responds to build and development issues, treating problems with build scripts or tooling as blocking concerns that warrant immediate fixes.