Infinitely extensible mahjong web client.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
EpicOrange/riichi_advanced has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in EpicOrange/riichi_advanced 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 7.5 places EpicOrange/riichi_advanced in the D tier.
The external contributor pull request merge rate for EpicOrange/riichi_advanced is 0.0%, based on public PR activity from non-core contributors.
EpicOrange/riichi_advanced currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Elixir project in EpicOrange/riichi_advanced 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/EpicOrange/riichi_advanced?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
The following bugs for American Mah-Jongg (NMJL) are known: [FIXED] Scoring on self-draws ends up being multiplied by 8 instead of 2 (see #114) [FIXED] Nearest Hands display does not take into account drawn tile (see #119) [FIXED] Nearest Hands display does not always suggest possible hands (see #110) Nearest Hands display only shows East for hands that are defined with Z for "any wind" Nearest Hands display does not always correctly display hands that are defined with 0 (see example in replies) Double-pairs and double-pungs are incorrectly evaluated (see #111) Card-Free mod is very broken (see #109) [FIXED] Auto-JC button sometimes skips valid calls (haven't properly investigated) Some wins aren't recognised (see examples in replies) The following features for American Mah-Jongg (NMJL) have been requested: Nearest Hands and Show Waits displays should also display the score of the hand. Additional hand match specifications, to handle other Cards: "A", "P", "K", "Q" for
Just thought I should document this bug here. It's been known for a while now, but I only noticed last week that it's also affecting the site itself (not just my local testing instance). This bug affects just about every variant that uses a joker in some way: American Vietnamese Bloody 30-Faan Jokers Malaysian Sakicards and probably a bunch more. Specifically, whenever a player would win with a joker in hand, the joker solver is called. (Note that it is perfectly possible for a player to win in these variants without jokers.) However, during this process, the joker solver often crashes. Sometimes, it's because the joker solver appears to be fed a nil tile (not sure why, haven't been able to reliably reproduce this version of the error). Other times, the joker solver crashes right at the final get-value step. This appears to be a bug (or multiple bugs?) in the Elixir parts of the code (more specifically, probably in smt.ex), and my knowledge of Elixir is insufficient to further diagno
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 EpicOrange/riichi_advanced, 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 EpicOrange/riichi_advanced acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
EpicOrange/riichi_advanced has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 7.5 places EpicOrange/riichi_advanced in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, EpicOrange/riichi_advanced 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 EpicOrange/riichi_advanced 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.