Customizable, privacy‑first, open-source clock app inspired by AOSP Clock
C-Rank Grade: D (Risky) - 30/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
BlackyHawky/Clock has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in BlackyHawky/Clock 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 29.9 places BlackyHawky/Clock in the D tier.
The external contributor pull request merge rate for BlackyHawky/Clock is 0.0%, based on public PR activity from non-core contributors.
BlackyHawky/Clock currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in BlackyHawky/Clock.
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/BlackyHawky/Clock?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Bug description some circle button can't be selected by talkback: the 'Add alarm' in alarm tab the 'Cities' in clock tab the 'Start' and 'Add timer' in timer tab the 'Start', 'Pause', 'Reset', 'Lap' and 'Share' in stopwatch tab Steps to reproduce open talkback try to select the big circle button like adding alarm it doesn't work,can't be selected Logs (optional but highly recommended) No response App version 2.31 Install Source GitHub Device model redmiNote9 Android version android12 Checklist I searched for existing issues (open and closed) before filing this report. I have read and understood the contribution guidelines. I have provided all required details. I understand that the feature request will be dismissed otherwise.
Bug description The icon for the timer animation is different than the static one. It is slightly larger and thinner. This is a minor detail, so no rush to fix! I wasn't totally sure whether to submit this as a bug or not. Steps to reproduce Go to another page Open the timer page Notice that the animated icon is different Logs (optional but highly recommended) No response App version 2.30.1 Install Source IzzyOnDroid Device model Multiple Android version Multiple Checklist I searched for existing issues (open and closed) before filing this report. I have read and understood the contribution guidelines. I have provided all required details. I understand that the feature request will be dismissed otherwise.
Feature idea Can this widget be added? Checklist I searched for existing issues (open and closed) before filing this report. I have read and understood the contribution guidelines. I have provided all required details. I understand that the feature request will be dismissed otherwise.
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 BlackyHawky/Clock, 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 BlackyHawky/Clock acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
BlackyHawky/Clock has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 29.9 places BlackyHawky/Clock in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, BlackyHawky/Clock currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for BlackyHawky/Clock 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.