Lichess mobile app
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 73%
Response Time: -
First Timer Success: 67%
lichess-org/mobile has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in lichess-org/mobile 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 69.4 places lichess-org/mobile in the A tier.
The external contributor pull request merge rate for lichess-org/mobile is 73.4%, based on public PR activity from non-core contributors.
lichess-org/mobile currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in lichess-org/mobile. Prompt code reviews with positive guidance for new contributors.
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/lichess-org/mobile?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (92% approval). Large PRs (>500 lines) take ~115 hours (33% approval). Keep your diff compact for rapid review.
A recent server change added the annotator to every move in studies: It is distracting so we should filter this out and probably display the annotator only when the move is long pressed and the bottom scroll sheet is opened.
What is the problem? This seems to only be a minor UI bug. On the analysis board, when a pawn reaches 8th (or 1st) rank, the promotion piece selector appears. If previous position button is clicked before selecting a piece, the selector remains visible even though we are on a previous position. The color of promotion pieces also sometimes changes between black and white This behavior is not present in live games. Steps to reproduce the bug Open analysis board, then move until a pawn reaches 8th or 1st rank Promotion piece selector appears. Do not select a piece. Click previous position button once or more times The promotion piece selector remains visible and its piece color may vary between black and white App version 0.26.6 Device Info IOS Additional information ScreenRecording_08-26-2026.01-37-35_1.mp4
What is the problem? Available pieces tray to drop is pushed down and not available. It’s when the time gets down to ten second and the clocks starts doing milliseconds. It uses too much space for the milliseconds(too large). I am not able to select/drag/drop pieces when this happened. I am using iPhone latest iOS app. Steps to reproduce the bug Play a crazy house game. when game goes below ten second. App version 0.26.6 Device Info iPhone 12 Pro Max - iOS 26.6.0 Additional information No response
Message and flag icons are too similar and easily confused. Suggest changing message icon to a rounded speech bubble which is more common. Suggest changing flag icon to be "filled in" so that it looks more like a white surrender flag.
Currently it's only possible to have mirrored pieces or to flip the board between moves. I think it makes sense to also have a mode for having the player view always at the bottom, so people can pass the phone back and forth and have their view look normal for their turn. This may require rework of the menu options too so it's clear.
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 lichess-org/mobile, 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 lichess-org/mobile acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.4% were successfully merged into the primary branch.
lichess-org/mobile has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming 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 69.4 places lichess-org/mobile in the Welcoming tier.
The external pull request merge rate is 73.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, lichess-org/mobile currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for lichess-org/mobile 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.