A nimble Mastodon web client
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 58%
Response Time: -
First Timer Success: 100%
elk-zone/elk has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in elk-zone/elk 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 59.4 places elk-zone/elk in the A tier.
The external contributor pull request merge rate for elk-zone/elk is 58.3%, based on public PR activity from non-core contributors.
elk-zone/elk currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in elk-zone/elk 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/elk-zone/elk?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~18 hours (73% approval). Large PRs (>500 lines) take ~135 hours (26% approval). Keep your diff compact for rapid review.
Describe the bug It's not possible to remove an audio attachment to a post from the UI, no button visible (see first screen capture of edit UI). When encountering a server error when trying to post (for example: file too big, cannot upload more than one audio attachment), then it is impossible to go back to a working state for the UI, as there is no button to reset the post form altogether as well. Since the draft is persisted, no amount of navigation, logging out and logging in can fix the state, and it's then impossible to post with that account. To Reproduce Steps to reproduce the behavior: Go to Home Click on text area for post Add audio attachment (.mp3, .ogg, .wav for example) click "edit" no button available to remove media, as would be there for visual attachments. Add another audio media click Post Get server error (usually file too big or cannot upload 2 audio attachments with Mastodon) It is now impossible to fix the state. Expected behavior a "remove" button is avail
Discussed in #2403 Originally posted by wiesehahn September 19, 2023 Is there any documentation about possible markdown syntax? For example it seems that bold text is supported, but lists are not rendered.
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 elk-zone/elk, 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 elk-zone/elk acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 58.3% were successfully merged into the primary branch.
elk-zone/elk has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming 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 59.4 places elk-zone/elk in the Welcoming tier.
The external pull request merge rate is 58.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, elk-zone/elk 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 elk-zone/elk 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.