NUnit Console runner and test engine
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 91%
Response Time: 4h
First Timer Success: 100%
nunit/nunit-console 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 nunit/nunit-console respond to incoming external pull requests in approximately 4.2 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 65.8 places nunit/nunit-console in the A tier.
The external contributor pull request merge rate for nunit/nunit-console is 90.9%, based on public PR activity from non-core contributors.
nunit/nunit-console does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in nunit/nunit-console. Prompt code reviews with positive guidance for new contributors.
Discussions in nunit/nunit-console focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/nunit/nunit-console?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~20 hours (41% approval). Keep your diff compact for rapid review.
Hi all, Sorry that it took soo long, but we got distracted to other topics; but now our UI tests got the focus again. I would like to duplicate issue nunit/nunit#4240 to this repo, as requested by the übergod of the project :) We live with a large .net framework legacy codebase, where we do have the runner and the tested app using the same old .net fw version. Also, we have integration tests with winforms/QT elements, and QT started throwing AccessViolationExceptions if the non-default thread starts messing with the QT classes... Even if we use --inprocess --workers=1 --agents=1 , and the test is configured with everything we managed to find in this area ((( [assembly: Apartment(ApartmentState.STA)][Apartment(ApartmentState.STA)] [SingleThreaded] [STAThread] ; remove all [RequiresThread] ))) ... The situation was the same: the Main thread started a new worker thread for running the test; even if setup+test+teardown was single-threaded, QT still throws AccessViolationException because
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 nunit/nunit-console, 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 nunit/nunit-console acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.9% were successfully merged into the primary branch.
nunit/nunit-console 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 ~4 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 65.8 places nunit/nunit-console in the Welcoming tier.
The external pull request merge rate is 90.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
nunit/nunit-console does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for nunit/nunit-console 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.