Mlem for Lemmy
C-Rank Grade: S (Elite) - 75/100
External PR Merge Rate: 95%
Response Time: 9h
First Timer Success: 100%
mlemgroup/mlem has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mlemgroup/mlem respond to incoming external pull requests in approximately 9.1 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 75.4 places mlemgroup/mlem in the S tier.
The external contributor pull request merge rate for mlemgroup/mlem is 95.1%, based on public PR activity from non-core contributors.
mlemgroup/mlem currently has 17 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in mlemgroup/mlem. Prompt code reviews with positive guidance for new contributors.
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/mlemgroup/mlem?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 Tuesday - Thursday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (96% approval). Large PRs (>500 lines) take ~44 hours (43% approval). Keep your diff compact for rapid review.
Requirements There are no existing issues for this bug report. Description Unlike when creating a post or comment, you cannot collapse the input window. Mlem Version Mlem 2.6 (913)
Requirements There are no existing issues for this feature. This is a request for a single feature (create multiple issues for multiple feature requests). Description Currently if I tap the select text icon while replying to a post that was created with an image the selectable text starts with the post title, then skips to the first line, if any of the post. The url for the image is not provided. Any images in the post itself are included however. The same is true for a post created with a non image link.
This setting already exists under Settings -> Comment. We should also include it under accessibility settings
Remove PinnedSortTracker.main. Instead, initialise it as a property of a high-level view and attach it to the SwiftUI environment. In all places where PinnedSortTracker.main is currently used, access the object from the environment instead.
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 mlemgroup/mlem, 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 mlemgroup/mlem acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 95.1% were successfully merged into the primary branch.
mlemgroup/mlem has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 75.4 places mlemgroup/mlem in the Elite tier.
The external pull request merge rate is 95.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mlemgroup/mlem currently has 17 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for mlemgroup/mlem 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.