Nix, the purely functional package manager
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 64%
Response Time: -
First Timer Success: 63%
NixOS/nix has a recorded first-timer success rate of 63.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in NixOS/nix respond to incoming external pull requests in approximately 0.0 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.8 places NixOS/nix in the A tier.
The external contributor pull request merge rate for NixOS/nix is 63.9%, based on public PR activity from non-core contributors.
NixOS/nix currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in NixOS/nix. Maintains strict focus on technical quality and test standards.
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/NixOS/nix?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (80% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Describe the bug When passing --option use-xdg-base-directories to certain nix-env subcommands like --install, a warning is erroneously printed. Steps To Reproduce Running a WIP of my script with set -x: + /nix/store/23zk8sgzamrbmj1fday15szf7f2279s8-nix-2.34.7/bin/nix-env --version nix-env (Nix) 2.34.7 + /nix/store/23zk8sgzamrbmj1fday15szf7f2279s8-nix-2.34.7/bin/nix-env --query [buncha stuff from my actual profile; the script has already overridden XDG_STATE_HOME but use-xdg-base-directories is false] + env + fgrep XDG_STATE_HOME XDG_STATE_HOME=/home/yoshi/example + /nix/store/23zk8sgzamrbmj1fday15szf7f2279s8-nix-2.34.7/bin/nix-env --option use-xdg-base-directories true --query [empty] + /nix/store/23zk8sgzamrbmj1fday15szf7f2279s8-nix-2.34.7/bin/nix-env --option use-xdg-base-directories true --install --file /home/yoshi/Documents/myEnv/binutils.nix warning: ignoring the client-specified setting 'use-xdg-base-directories', because it is a restricted setting and you are not a trusted use
Is your feature request related to a problem? Some packages have multiple binaries with different purposes therefore setting mainProgram is not desirable. When mainProgram is not set for these packages nix run errors out with error: unable to execute '/nix/store/abc/bin/xyz': No such file or directory Proposed solution A new error for packages that don't have the mainProgram attribute set, something like error: in 'abc': 'mainProgram' isn't set Alternative solutions An option to set mainProgram to null for packages that desire to do so, leaving the default behavior of mainProgram = pname; intact. An error like error: 'abc' doesn't have a default binary would be better in this case. Additional context NixOS/nixpkgs#486543 Checklist checked latest Nix manual (source) checked open feature issues and pull requests for possible duplicates Add 👍 to issues you find important.
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 NixOS/nix, 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 NixOS/nix acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.9% were successfully merged into the primary branch.
NixOS/nix has a recorded first-timer success rate of 63.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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.8 places NixOS/nix in the Welcoming tier.
The external pull request merge rate is 63.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, NixOS/nix 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 NixOS/nix 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.