Markdown renderer for Kotlin Multiplatform Projects (Android, iOS, Desktop), using Compose.
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 86%
Response Time: <1h
First Timer Success: 100%
mikepenz/multiplatform-markdown-renderer 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 mikepenz/multiplatform-markdown-renderer respond to incoming external pull requests in approximately 0.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 72.7 places mikepenz/multiplatform-markdown-renderer in the S tier.
The external contributor pull request merge rate for mikepenz/multiplatform-markdown-renderer is 86.0%, based on public PR activity from non-core contributors.
mikepenz/multiplatform-markdown-renderer currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in mikepenz/multiplatform-markdown-renderer. 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/mikepenz/multiplatform-markdown-renderer?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13: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 ~4 hours (96% approval). Large PRs (>500 lines) take ~0 hours (39% 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 Kotlin.
A modern Android video player powered by libmpv, built with Jetpack Compose.
No repository description available.
🤖 Wire client for Android
Bug Description Talkback announces things like "start X pixels" as user navigates markdown content Steps to Reproduce Steps to reproduce the behavior: Run sample Android app Turn on talkback use swipe navigation to listen to content Expected Behavior Talkback does not contain layout information (if that's what it is?) like "start 100 pixels" or "end 100 pixels" that may confuse a talkback user. Actual Behavior Talkback announces things like "start 100 pixels" or "end 100 pixels". Screenshots (turn on player audio to hear talkback) talkback_pixels.mp4 Environment Library Version: 3.38.1 Platform: Android Device: Pixel 7 Pro OS Version: Android 16 Kotlin Version: [not sure, I'm on commit bed5ff5 in the sample app] Kotlin Version: [not sure, I'm on commit bed5ff5 in the sample app] Checklist I have searched for similar issues I have checked the sample application I have read the README I have checked the CHANGELOG I have read the MIGRATION GU
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 mikepenz/multiplatform-markdown-renderer, 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 mikepenz/multiplatform-markdown-renderer acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.0% were successfully merged into the primary branch.
mikepenz/multiplatform-markdown-renderer 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 ~<1 hour. 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 72.7 places mikepenz/multiplatform-markdown-renderer in the Elite tier.
The external pull request merge rate is 86.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mikepenz/multiplatform-markdown-renderer 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 mikepenz/multiplatform-markdown-renderer 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.