The Wikimedia Commons Android app allows users to upload pictures from their Android phone/tablet to Wikimedia Commons
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 34%
Response Time: 8d
First Timer Success: 35%
commons-app/apps-android-commons has a recorded first-timer success rate of 35.3%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in commons-app/apps-android-commons respond to incoming external pull requests in approximately 194.9 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 46.6 places commons-app/apps-android-commons in the B tier.
The external contributor pull request merge rate for commons-app/apps-android-commons is 33.6%, based on public PR activity from non-core contributors.
commons-app/apps-android-commons currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in commons-app/apps-android-commons. Maintains strict focus on technical quality and test standards.
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/commons-app/apps-android-commons?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 Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15: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 ~127 hours (42% approval). Large PRs (>500 lines) take ~935 hours (15% 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 Kotlin.
New Guise
Native Android app for Habitica
Android screen and sound recording/streaming app
856510a8-2c99-4a81-bb84-fb072f28db81.mp4 f5eb5f50-627b-43c6-b57e-461b12b89492.mp4
I am surprised our CI did not catch this basic mistake: #6822
Description It appears that the CI workflow responsible for welcoming new contributors is consistently being skipped. As a result, first-time contributors are not receiving the intended welcome message. Expected Behavior The workflow should trigger for first-time contributors and post a welcome message automatically. Actual Behavior The workflow is skipped, even when a new contributor opens their first PR. See this PR CI : #6747 Steps to Reproduce Create a pull request from a first-time contributor account Observe the CI workflow execution Notice that the welcome workflow is skipped
Problem: Nearby labels currently hold in static memory a Map of 1000+ Strings such as "Q12345". Optimization idea: Hold QIDs as integers rather than Strings. Have them already sorted in the resource XML and use binary search to retrieve them. This AI-generated draft pull request may serve as inspiration, though it is not perfect: #6722 A few problems: That PR should modify the XML files to sort the QIDs. That PR sorts the QIDs dynamically. Instead we should consider the array as sorted already. Some kind of static check should be done at build time, perhaps as a unit test.
Commons gets too many frivolous deletion requests from our app. Let's make it mandatory to enter a justification. Both when deleting from Media Details or from Review.
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 commons-app/apps-android-commons, 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 commons-app/apps-android-commons acknowledge new external contributions in approximately 8 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.6% were successfully merged into the primary branch.
commons-app/apps-android-commons has a recorded first-timer success rate of 35.3%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 days+. 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 46.6 places commons-app/apps-android-commons in the Solid tier.
The external pull request merge rate is 33.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, commons-app/apps-android-commons currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for commons-app/apps-android-commons 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.