Powerful .NET library for benchmarking
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 85%
Response Time: 8h
First Timer Success: 100%
dotnet/BenchmarkDotNet has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dotnet/BenchmarkDotNet respond to incoming external pull requests in approximately 7.7 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 68.8 places dotnet/BenchmarkDotNet in the A tier.
The external contributor pull request merge rate for dotnet/BenchmarkDotNet is 85.0%, based on public PR activity from non-core contributors.
dotnet/BenchmarkDotNet 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/dotnet/BenchmarkDotNet?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
On current version of BenchmarkDotNet implementation. --affinity command line argument is parsed as int (signed). So it can't accept value that over int.MaxValue value and it can't specify over 32-processor affinity. BenchmarkDotNet/src/BenchmarkDotNet/ConsoleArguments/CommandLineOptions.cs Line 67 in b515068 public int? Affinity { get; set; } I thought, it need to change affinity parameter to nuint (unsigned) to pass affinity as bit mask. Note: Currently BenchmarkDotNet seems not support CPU groups. So affinity can set up to 64 logical CPU cores. BenchmarkDotNet/src/BenchmarkDotNet/Extensions/ProcessExtensions.cs Lines 45 to 46 in b515068 // Max supported affinity without CPU groups is 64 long cpuMask = Environment.ProcessorCount >= 64 ? un
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 dotnet/BenchmarkDotNet, 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 dotnet/BenchmarkDotNet acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.0% were successfully merged into the primary branch.
dotnet/BenchmarkDotNet has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 68.8 places dotnet/BenchmarkDotNet in the Welcoming tier.
The external pull request merge rate is 85.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dotnet/BenchmarkDotNet 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 dotnet/BenchmarkDotNet 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.