Scribe-Android: Keyboards for language learners & Conjugate-Android: Wikidata based verb conjugation app
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 75%
Response Time: 1d
First Timer Success: 80%
scribe-org/Scribe-Android has a recorded first-timer success rate of 80.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in scribe-org/Scribe-Android respond to incoming external pull requests in approximately 25.7 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 64.4 places scribe-org/Scribe-Android in the A tier.
The external contributor pull request merge rate for scribe-org/Scribe-Android is 74.5%, based on public PR activity from non-core contributors.
scribe-org/Scribe-Android currently has 11 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing C++ project in scribe-org/Scribe-Android 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/scribe-org/Scribe-Android?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (93% approval). Large PRs (>500 lines) take ~123 hours (34% approval). Keep your diff compact for rapid review.
Terms I have searched open and closed feature requests I agree to follow Scribe-Android's Code of Conduct Description In the latest work on Scribe-Data we needed to add in nouns and verbs fields to the contracts to allow for queries to be generated from them. See below for the new structure: nouns: # we add a nouns top key genders: ... numbers: ... verbs: # we add a verbs top key conjugations: ... We now need to update Scribe-Android to use these new contract fields that are above the old ones. Contribution Happy to support and review a PR! 🚀
Terms I have searched all open bug reports I agree to follow Scribe-Android's Code of Conduct Behavior ClipboardMonitor creates a CoroutineScope(Dispatchers.Main) that is never cancelled, and onDestroy() doesn't stop it. Its listener and coroutines can keep the service context alive. Device type Pixel 9 Versions No response
Terms I have searched all open bug reports I agree to follow Scribe-Android's Code of Conduct Behavior These four keyboards redeclare hasTextBeforeCursor as a stored field, which hides the live getter. The value is set once in onStartInput and then goes stale. Device type Pixel 9 Versions No response
Terms I have searched all open bug reports I agree to follow Scribe-Android's Code of Conduct Behavior The left and right arrow keys take the cursor position from getTextBeforeCursor(1000), which returns at most 1,000 characters. Device type Tablet Versions No response
Terms I have searched all open bug reports I agree to follow Scribe-Android's Code of Conduct Behavior In reviewing #692 I discovered that there's an issue with how the keyboard is being loaded now, which is likely from the work that was done for #426. I let one of those PRs sneak in with a bug (sorry). Assumption now is that this should be easy to fix, especially as the code is now more modular. See screenshot below: Device type Pixel 9 emulator Versions API 36
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 scribe-org/Scribe-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 scribe-org/Scribe-Android acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.5% were successfully merged into the primary branch.
scribe-org/Scribe-Android has a recorded first-timer success rate of 80.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 64.4 places scribe-org/Scribe-Android in the Welcoming tier.
The external pull request merge rate is 74.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, scribe-org/Scribe-Android currently has 11 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for scribe-org/Scribe-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.