Swagger tools for documenting API's built on ASP.NET Core
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 76%
Response Time: 2h
First Timer Success: 60%
domaindrivendev/Swashbuckle.AspNetCore has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in domaindrivendev/Swashbuckle.AspNetCore respond to incoming external pull requests in approximately 1.5 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 63.9 places domaindrivendev/Swashbuckle.AspNetCore in the A tier.
The external contributor pull request merge rate for domaindrivendev/Swashbuckle.AspNetCore is 75.8%, based on public PR activity from non-core contributors.
domaindrivendev/Swashbuckle.AspNetCore currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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/domaindrivendev/Swashbuckle.AspNetCore?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Is your feature request related to a specific problem? Or an existing feature? I have enums with comments on their enum members. It would be nice to see this comments in the OpenAPI document. Example enum: public enum MyStatus { /// <summary> /// Comment on value /// </summary> Value, /// <summary> /// Other comment /// </summary> OtherValue } Describe the solution you'd like According to the spec this is not possible with how enums are currently generated (with an enum array). But the spec describes an alternative way that allows enum member descriptions (oneOf or anyOf with const values). Here is also an example: OAI/OpenAPI-Specification#348 (comment) As I understand it this would only be allowed in OpenAPI v3.1 mode. So the older modes would have to stay as they are. The chosen solution should also be supported by popular OpenAPI UIs (Swagger UI, Scalar, ...) Additional context Maybe the Description attribute should be supported in addition to XML d
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 domaindrivendev/Swashbuckle.AspNetCore, 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 domaindrivendev/Swashbuckle.AspNetCore acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.8% were successfully merged into the primary branch.
domaindrivendev/Swashbuckle.AspNetCore has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 hours. 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 63.9 places domaindrivendev/Swashbuckle.AspNetCore in the Welcoming tier.
The external pull request merge rate is 75.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, domaindrivendev/Swashbuckle.AspNetCore currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for domaindrivendev/Swashbuckle.AspNetCore 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.