Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 52%
Response Time: 10h
First Timer Success: 30%
nim-lang/Nim has a recorded first-timer success rate of 30.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nim-lang/Nim respond to incoming external pull requests in approximately 9.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 62.7 places nim-lang/Nim in the A tier.
The external contributor pull request merge rate for nim-lang/Nim is 52.4%, based on public PR activity from non-core contributors.
nim-lang/Nim currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
Highly welcoming maintainers in nim-lang/Nim. Prompt code reviews with positive guidance for new contributors.
Discussions in nim-lang/Nim 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/nim-lang/Nim?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (66% approval). Large PRs (>500 lines) take ~46 hours (24% approval). Keep your diff compact for rapid review.
Nim Version 023bd63, at least 0.9 Description Nim/lib/pure/strutils.nim Line 2557 in 2ac83c7 buf {.noinit.}: array[0..2500, char] It was increased from 80 because of #398, but also the example in #398 doesn't work because the precision argument is limited to a max of 32. Also thanks to #23322 snprintf is now used, which doesn't error if the output does not fit in the buffer. This doesn't seem to be a huge issue but maybe it is still worth shrinking the buffer. Feel free to close otherwise. Current Output Expected Output Known Workarounds No response Additional Information No response
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 nim-lang/Nim, 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 nim-lang/Nim acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 52.4% were successfully merged into the primary branch.
nim-lang/Nim has a recorded first-timer success rate of 30.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 62.7 places nim-lang/Nim in the Welcoming tier.
The external pull request merge rate is 52.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nim-lang/Nim 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 nim-lang/Nim 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.