A privacy-conscious Android keyboard made for your thumbs
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 92%
Response Time: 8h
First Timer Success: 86%
dessalines/thumb-key has a recorded first-timer success rate of 85.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dessalines/thumb-key respond to incoming external pull requests in approximately 7.6 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 70.9 places dessalines/thumb-key in the S tier.
The external contributor pull request merge rate for dessalines/thumb-key is 92.1%, based on public PR activity from non-core contributors.
dessalines/thumb-key currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in dessalines/thumb-key. Ensure PR scope matches issue requirements closely before requesting review.
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/dessalines/thumb-key?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Describe your suggested feature Bottom/Top and Left/Right are valid keyActions but not Up/Down for some reason Other details Up/Down should exist, Bottom/Top should be to go to the very top or the very bottom of the document Acknowledgements I have written a short but informative title. I have updated the app to the latest version. I have checked through the app settings for my feature. I have searched the existing issues and this is a new one, NOT a duplicate or related to another open issue. This is a single feature request, in case of multiple feature requests I will open a separate issue for each one (they can always link to each other if related) This is not a question or a discussion, in which case I should have gone to lemmy.ml/c/thumbkey I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements. 🤡 I will fill out all of the requested information in this form.
Steps to reproduce As mentioned in #1675, key actions like ToggleNumericMode are confusingly named because their action is idempotent, unlike an actual toggle which goes back and forth between an ON/OFF state. A better name would be something like SetNumericMode or something similar. Expected behavior N/A Actual behavior N/A version of the program 5.0.11 Android version N/A Device N/A Other details No response Acknowledgements I have written a short but informative title. I have updated the app to the latest version. I have searched the existing issues and this is a new one, NOT a duplicate or related to another open issue. This is not a question or a discussion, in which case I should have gone to lemmy.ml/c/thumbkey This is a single bug report, in case of multiple bugs I will open a separate issue for each one (they can always link to each other if related) I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements. 🤡 I have
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 dessalines/thumb-key, 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 dessalines/thumb-key acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 92.1% were successfully merged into the primary branch.
dessalines/thumb-key has a recorded first-timer success rate of 85.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 hours. 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 70.9 places dessalines/thumb-key in the Elite tier.
The external pull request merge rate is 92.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dessalines/thumb-key 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 dessalines/thumb-key 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.