Paradise Station's GitHub main repository.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 13%
Response Time: 12h
First Timer Success: 27%
ParadiseSS13/Paradise has a recorded first-timer success rate of 27.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ParadiseSS13/Paradise respond to incoming external pull requests in approximately 12.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 58.6 places ParadiseSS13/Paradise in the A tier.
The external contributor pull request merge rate for ParadiseSS13/Paradise is 12.7%, based on public PR activity from non-core contributors.
ParadiseSS13/Paradise currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in ParadiseSS13/Paradise 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/ParadiseSS13/Paradise?utm_source=github&utm_medium=badge)
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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (16% approval). Large PRs (>500 lines) take ~60 hours (15% approval). Keep your diff compact for rapid review.
BYOND Version N/A Issue Description There are 2 medkits in robotics for constructing medbots. What did you expect to happen? for there to be 3 medkits in robotics to construct 3 medbots. What happened instead? there are only 2 Why is this bad/What are the consequences? Most other stations (to my knowledge) have 3 medkits with the 3 health analyzers and 3 proximity sensors. Seems weird for this station which is pretty large to have less medbots. Steps to reproduce the issue. look at NSS Kerberos robotics When did the problem start happening? probably the last time robotics was majorly touched Extra information What is mot weird is that there are 3 health analyzers and 3 proximity sensors, but not 3 medkits. Relevant log output/runtime error
What did you expect to happen? I expected to not be able to use the ghost confirmation popup after leaving the cryopod. What happened instead? I could exit the cryopod and ghost where ever I felt like. Why is this bad/What are the consequences? You probably shouldn't be able to use the cryo button outside of cryo. Steps to reproduce the issue: Enter a cryopod Click the ghost popup on the left side of the scren Exit the cryopod Click the 'ghost' button Attached logs N/A Additional details Author: Iramoye Approved By: pollardthedragon Round ID: 48717 Client BYOND Version: 516.1673 Server BYOND Version: 516.1666 Server commit: 57ae8c6 Active Test Merges: #31765 at 8101c62 #31439 at 0bad1d8 #31929 at 9f07192 #31658 at 215dbaa #31984 at 4d4cc00 Note: None
BYOND Version 516.1677 Issue Description Disposals routing for Janitor closet deliveries (from disposals) spits out in the Trainer's office. What did you expect to happen? Janitors Closet What happened instead? Trainer Office Why is this bad/What are the consequences? All those Bluespace Light Replacers are going to undeserving Mentors instead of the hardworking Janitors. Steps to reproduce the issue. Either try to mail yourself as a drone to the Janitor's office from disposals or mail anything from disposals to the Janitor's office. Check the Trainer Office and find the package. When did the problem start happening? Not sure. Extra information If you mail yourself from the library you DO end up in the Janitor's office. There is a sort junction just north of the Fore East Hallway APC that's labeled Janitor Closet. Relevant log output/runtime error
BYOND Version 516.6(81?) It gets cut off by the "ok" after the second 6 Issue Description In this round MMI radio upgrades suddenly stopped installing. It will say it is installing and installed but then drop the upgrade chip on the ground. This wasn't happening in the previous round where we tested the small station. What did you expect to happen? I expected the upgrade to apply to the MMI What happened instead? The upgrade dropped onto the ground, yet there was still a log that said tit was working Why is this bad/What are the consequences? Upgrades should apply to things. Makes it so you can't use the radio to communicate in an MMI even when the roboticist tried to install one Steps to reproduce the issue. Get MMI with no radio, attempt to put it in the MMI. Get extremely confused because it worked mere moments ago When did the problem start happening? Exactly now. Like the previous round with the small station had it work Extra information No response Relevant log output/runtime er
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 ParadiseSS13/Paradise, 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 ParadiseSS13/Paradise acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 12.7% were successfully merged into the primary branch.
ParadiseSS13/Paradise has a recorded first-timer success rate of 27.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 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 58.6 places ParadiseSS13/Paradise in the Welcoming tier.
The external pull request merge rate is 12.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ParadiseSS13/Paradise 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 ParadiseSS13/Paradise 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.