Mlem for Lemmy
C-Rank Grade: S (Elite) - 78/100
External PR Merge Rate: 99%
Response Time: 10h
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.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 78.3 places mlemgroup/mlem in the S tier.
The external contributor pull request merge rate for mlemgroup/mlem is 99.2%, based on public PR activity from non-core contributors.
mlemgroup/mlem currently has 13 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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (96% approval). Large PRs (>500 lines) take ~46 hours (45% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Swift.
iOS App for Bangumi
The Movie Database Swift Package
Application which is main API component for Vernissage photos sharing platform.
If the cursor is at the end of a non-empty line and you tap the "spoiler" button, it adds the spoiler tag on the current line, which is invalid. It should make a new line for it instead in this case.
This would remove the need to scroll to access it. I'm guessing this one is used quite frequently, and should get higher priority as a result It could go just after the undo/redo buttons, maybe with a divider following it
At the moment, there's a single trailing "mark read" swipe action. It does not follow the inbox swipe configuration
It's inconsistent with the rest of the subscription list
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, 99.2% 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 78.3 places mlemgroup/mlem in the Elite tier.
The external pull request merge rate is 99.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mlemgroup/mlem currently has 13 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.