.NET API Gateway
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 25%
Response Time: <1h
First Timer Success: -
ThreeMammals/Ocelot has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ThreeMammals/Ocelot respond to incoming external pull requests in approximately 0.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 51.5 places ThreeMammals/Ocelot in the B tier.
The external contributor pull request merge rate for ThreeMammals/Ocelot is 25.0%, based on public PR activity from non-core contributors.
ThreeMammals/Ocelot currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in ThreeMammals/Ocelot welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/ThreeMammals/Ocelot?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (31% approval). Large PRs (>500 lines) take ~0 hours (15% approval). Keep your diff compact for rapid review.
Description Ocelot 25.0.1 has a dependency on Microsoft.Extensions.DiagnosticAdapter >= 3.1.32. Microsoft.Extensions.DiagnosticAdapter 3.1.32 was last updated in December 2022 and is from the .NET Core 3.1 generation. It has no maintained stable successor version that can be used to upgrade the dependency. Ocelot 25.0.1 currently declares this dependency even for its net10.0 target. The dependency is used by Ocelot's diagnostic-listener integration (OcelotMiddlewareExtensions.ConfigureDiagnosticListener). Impact Applications using Ocelot 25.0.1 and targeting .NET 10 continue to receive EOL/obsolete dependency findings for Microsoft.Extensions.DiagnosticAdapter 3.1.32. Because there is no maintained stable version of Microsoft.Extensions.DiagnosticAdapter to upgrade to, applications cannot resolve the finding through a normal NuGet package upgrade or version override. This is particularly problematic for applications with security/compliance requirements that require all dependencies to
Predecessor #2407 Idea 💡 Proposal — merge the WebSocket and HTTP pipelines Status: planning only. This draft intentionally contains no implementation, tests, or documentation changes yet. It captures the goal and a proposed plan for discussion before any code is written. Opened per @raman-m's suggestion on #2406 to start the follow-up; no rush expected until the next release cycle. Goal Remove the forked WebSocket pipeline and route WebSocket upgrade requests through the same Ocelot pipeline as ordinary HTTP requests. This is the larger follow-up discussed on #2406 (the #2403 IP-security fix), where the fork was the root cause of the bypass. Why A WebSocket request is an ordinary HTTP request until AcceptWebSocketAsync. Today app.MapWhen(IsWebSocketRequest, ConfigureWebSockets) forks it into a hand-maintained subset of middlewares, which is why WS upgrades miss most Ocelot features (auth, authz, rate limiting, claims, header transforms) and why each gap has to be patched in th
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to ThreeMammals/Ocelot, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of ThreeMammals/Ocelot acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 25.0% were successfully merged into the primary branch.
ThreeMammals/Ocelot has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 51.5 places ThreeMammals/Ocelot in the Solid tier.
The external pull request merge rate is 25.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ThreeMammals/Ocelot currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ThreeMammals/Ocelot are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.