A lightweight Minecraft server written from scratch in Rust supporting Minecraft versions from 1.7.2 up to 26.2.
C-Rank Grade: C (Moderate) - 39/100
External PR Merge Rate: 67%
Response Time: -
First Timer Success: 50%
Quozul/PicoLimbo has a recorded first-timer success rate of 50.0%. Repositories ranked C typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Quozul/PicoLimbo 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 38.7 places Quozul/PicoLimbo in the C tier.
The external contributor pull request merge rate for Quozul/PicoLimbo is 66.7%, based on public PR activity from non-core contributors.
Quozul/PicoLimbo currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Rust project in Quozul/PicoLimbo welcoming community pull requests and bug fixes.
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/Quozul/PicoLimbo?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (83% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Rust.
Low latency inter-thread communication library in Rust inspired by the LMAX Disruptor.
An arbitrary-precision arithmetic library for Rust.
Base-16 Modified Patricia Merkle Tree (aka Trie)
Bedrock Edition should be supported when using Geyser installed on a proxy. However some users on Discord reported that it doesn't work well when using the standalone version of Geyser.
I thought that if we add a scoreboard where we can display information about limbo. I would also like to ask you to add a function to the velocity plugin that would immediately throw a server into limbo if it crashes. That would be great.
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 Quozul/PicoLimbo, 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 Quozul/PicoLimbo acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
Quozul/PicoLimbo has a recorded first-timer success rate of 50.0%. Repositories ranked Moderate 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 38.7 places Quozul/PicoLimbo in the Moderate tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Quozul/PicoLimbo currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Quozul/PicoLimbo 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.