A free online & offline learning platform to make quality education accessible for all.
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 50%
Response Time: 2d
First Timer Success: 22%
oppia/oppia-android has a recorded first-timer success rate of 22.2%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in oppia/oppia-android respond to incoming external pull requests in approximately 49.8 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 47.6 places oppia/oppia-android in the B tier.
The external contributor pull request merge rate for oppia/oppia-android is 49.6%, based on public PR activity from non-core contributors.
oppia/oppia-android currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (62% critical review signals). Ensure PRs strictly follow guidelines before requesting review in oppia/oppia-android.
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/oppia/oppia-android?utm_source=github&utm_medium=badge)
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 Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14: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 ~32 hours (62% approval). Large PRs (>500 lines) take ~239 hours (22% 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.
💊 An Android application to use ReVanced, Morphe and AmpleReVanced on that has extra features the official manager doesn't have
A KMP template of the New York Times App for Android, Desktop, iOS, Windows and Web
Media Gallery app for Android made with Jetpack Compose
Describe the bug When trying to build a release locally recently, I ran into a situation where my AAB ended up being assembled with negative version codes (per #6265). Steps To Reproduce Check out a shallow copy of Oppia Android. Try to build a release. Use bundletool to observe the version codes. Observe negative version codes. Expected Behavior Version codes should never be negative. In this case it's unavoidable since a shallow copy of the repository will have the wrong commit count on develop, however we should just have TransformAndroidManifest outright fail in these cases. Screenshots/Videos No response What device/emulator are you using? No response Which Android version is your device/emulator running? No response Which version of the Oppia Android app are you using? No response Additional Context No response
Describe the bug Since #6268 was merged, coderabbit is now enabled for opt-in reviews. However, coderabbit is a bit over-eager and announces itself for every PR. This adds a lot of email overhead for PRs, and seems largely unnecessary (and a bit spammy). Steps To Reproduce Create any PR and observe that coderabbit automatically posts a comment that it's disabled but can be used with the coderabbit review command. Expected Behavior It would be preferred if coderabbit didn't announce itself at all. This should be configurable using coderabbit settings. Screenshots/Videos No response What device/emulator are you using? No response Which Android version is your device/emulator running? No response Which version of the Oppia Android app are you using? No response Additional Context No response
Is your feature request related to a problem? Please describe. scripts/static_checks.sh is the local "run all checks" convenience script. However, when an individual check fails (e.g., ktlint_lint_check.sh exits with code 1), the outer script currently continues running the next check and ultimately exits with the status of the last command, not the first failure. This means a developer could see "finished" at the end while a check in the middle silently failed. The fix is to track failures across all checks and exit with a non-zero code if any of them failed, matching CI behavior. Describe the solution you'd like Update scripts/static_checks.sh to track failures across all checks and exit with a non-zero code if any of them failed, while still running all checks to completion (not bailing on the first failure). Concretely: Add a FAILURES=0 counter at the top of the script. After each check invocation, append || FAILURES=$((FAILURES+1)) to capture failures without stopping execution.
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 oppia/oppia-android, 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 oppia/oppia-android acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 49.6% were successfully merged into the primary branch.
oppia/oppia-android has a recorded first-timer success rate of 22.2%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 47.6 places oppia/oppia-android in the Solid tier.
The external pull request merge rate is 49.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, oppia/oppia-android 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 oppia/oppia-android 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.