A native pdf viewer for Windows and Linux (Wayland/X11) with configurable keybindings.
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 100%
Response Time: 10h
First Timer Success: -
vincent-uden/miro has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in vincent-uden/miro respond to incoming external pull requests in approximately 9.5 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 45.7 places vincent-uden/miro in the B tier.
The external contributor pull request merge rate for vincent-uden/miro is 100.0%, based on public PR activity from non-core contributors.
vincent-uden/miro currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in vincent-uden/miro. Reviews community pull requests with focus on project quality.
Discussions in vincent-uden/miro focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/vincent-uden/miro?utm_source=github&utm_medium=badge)
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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
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.
@tukanoidd somehow the nix build broke again when I bumped mupdf to 0.8.0. I really don't understand how to get any information out of these CI logs so I can't really give much more info than that. https://github.com/vincent-uden/miro/actions/runs/37845201702/job/113544233055
Some initial testing shows the release binary dropping from 37.2 MB to 26.9 MB. I can't feel any performance drop while using the program but this would require more tracy spans to find out for sure.
Using 2-finger panning does not work: when moving the fingers both up, miro also pans up, even though natural scrolling is enabled (same with left and right). Panning has no effect at all. OS: macOS Tahoe 26.5.1 (25F80) arm64 Host: MacBook Pro (14-inch, M5, 2025) Kernel: Darwin 25.5.0 Uptime: 5 days, 13 hours, 52 mins Packages: 158 (brew), 21 (brew-cask) Shell: zsh 5.9 Display (Color LCD): 3600x2338 @ 2x in 14", 120 Hz [Built-in] WM: Quartz Compositor 1.600.0 (with Yabai) WM Theme: Multicolor (Dark) Theme: Liquid Glass Font: .AppleSystemUIFont [System], Helvetica [User] Cursor: Fill - Black, Outline - White (32px) Terminal: kitty 0.47.1 Terminal Font: Menlo-Regular (9pt) CPU: Apple M5 (10) @ 4.61 GHz GPU: Apple M5 (10) @ 1.62 GHz [Integrated] Memory: 23.98 GiB / 32.00 GiB (75%) Swap: 3.51 GiB / 5.00 GiB (70%) Disk (/): 256.81 GiB / 926.30 GiB (28%) - apfs [Read-only] Battery (bq40z651): 88% (16 hours, 54 mins remaining) [Discharging] Locale: en_US.UTF-8
this problem happens on a fresh install on a new macbook: OS: macOS Tahoe 26.5.1 (25F80) arm64 Host: MacBook Pro (14-inch, M5, 2025) Kernel: Darwin 25.5.0 Uptime: 5 days, 13 hours, 52 mins Packages: 158 (brew), 21 (brew-cask) Shell: zsh 5.9 Display (Color LCD): 3600x2338 @ 2x in 14", 120 Hz [Built-in] WM: Quartz Compositor 1.600.0 (with Yabai) WM Theme: Multicolor (Dark) Theme: Liquid Glass Font: .AppleSystemUIFont [System], Helvetica [User] Cursor: Fill - Black, Outline - White (32px) Terminal: kitty 0.47.1 Terminal Font: Menlo-Regular (9pt) CPU: Apple M5 (10) @ 4.61 GHz GPU: Apple M5 (10) @ 1.62 GHz [Integrated] Memory: 23.98 GiB / 32.00 GiB (75%) Swap: 3.51 GiB / 5.00 GiB (70%) Disk (/): 256.81 GiB / 926.30 GiB (28%) - apfs [Read-only] Battery (bq40z651): 88% (16 hours, 54 mins remaining) [Discharging] Locale: en_US.UTF-8
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 vincent-uden/miro, 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 vincent-uden/miro acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
vincent-uden/miro has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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 45.7 places vincent-uden/miro in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vincent-uden/miro currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for vincent-uden/miro 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.