Hyperspace -- A mod for FTL: Faster than Light
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 82%
Response Time: 5h
First Timer Success: 100%
FTL-Hyperspace/FTL-Hyperspace has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in FTL-Hyperspace/FTL-Hyperspace respond to incoming external pull requests in approximately 4.6 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 73.9 places FTL-Hyperspace/FTL-Hyperspace in the S tier.
The external contributor pull request merge rate for FTL-Hyperspace/FTL-Hyperspace is 82.4%, based on public PR activity from non-core contributors.
FTL-Hyperspace/FTL-Hyperspace currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in FTL-Hyperspace/FTL-Hyperspace. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in FTL-Hyperspace/FTL-Hyperspace 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/FTL-Hyperspace/FTL-Hyperspace?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 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 ~4 hours (96% approval). Large PRs (>500 lines) take ~22 hours (37% approval). Keep your diff compact for rapid review.
I am entirely unsure why this even happens, but many texts from the japanese translation as an example, don't ever draw in japanese. Examples are the seed display or "No ship achievements": Chinese and Korean on the other hand seems to be working just fine:
As in title so the following code would work: choice hidden="true" req="CREW_SHIP_SLOT1_2" "Some kind of Menu option appear." This menu would appear if the Tully's Crewser B ship on page 14 is unlocked. Since the ids for ships are unique it should be easy to do.
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 FTL-Hyperspace/FTL-Hyperspace, 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 FTL-Hyperspace/FTL-Hyperspace acknowledge new external contributions in approximately 4 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.4% were successfully merged into the primary branch.
FTL-Hyperspace/FTL-Hyperspace has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 73.9 places FTL-Hyperspace/FTL-Hyperspace in the Elite tier.
The external pull request merge rate is 82.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, FTL-Hyperspace/FTL-Hyperspace 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 FTL-Hyperspace/FTL-Hyperspace 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.