An experiment in hermetic, reproducible build systems
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 89%
Response Time: 4d
First Timer Success: 100%
256lights/zb 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 256lights/zb respond to incoming external pull requests in approximately 102.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 60.7 places 256lights/zb in the A tier.
The external contributor pull request merge rate for 256lights/zb is 89.4%, based on public PR activity from non-core contributors.
256lights/zb currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in 256lights/zb. Reviews community pull requests with focus on project quality.
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/256lights/zb?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~67 hours (96% approval). Large PRs (>500 lines) take ~493 hours (40% approval). Keep your diff compact for rapid review.
Since I've built a general HTTP PUT mechanism, I'd like to have a command called zb store init that takes a single URL argument and creates a basic discovery document. (Perhaps as a -o/--output flag, with a default of local discovery.json?) This would make it easier for system administrators to set up a binary cache than reading a bunch of docs or using a separate tool (e.g. AWS/GCP CLI).
The Windows test workflow takes >10m to complete whereas it takes ~1m on Linux and macOS. The same test suite runs in 15 seconds on my Windows desktop. I'm not sure what the root-cause is, but for now, I'm going to bump up the timeout. #298 documents my attempted fixes.
It would be nice to be able to dump a GraphViz DOT file of the dependency tree for any set of derivations.
Similar to how zb derivation show accepts .drv file arguments, I want zb build and zb derivation env to accept .drv files from the store as arguments. This would help in debugging cases where I already have a derivation path (i.e. from build logs etc.) and don't want to trace through an entire Lua build graph to figure out how to name it. Requirements Passing a .drv file in the CLI's configured store directory as an argument to zb build causes all outputs of the derivation to be realized. If a URL fragment is present in a .drv file argument to zb build, then it is used as an output name instead of building all the outputs. Passing a .drv file in the CLI's configured store directory as an argument to zb derivation env evaluates that specific path.
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 256lights/zb, 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 256lights/zb acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 89.4% were successfully merged into the primary branch.
256lights/zb 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 days+. 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 60.7 places 256lights/zb in the Welcoming tier.
The external pull request merge rate is 89.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, 256lights/zb currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for 256lights/zb 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.