A modular and extensible wayland compositor
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 89%
Response Time: 11h
First Timer Success: 83%
WayfireWM/wayfire has a recorded first-timer success rate of 83.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in WayfireWM/wayfire respond to incoming external pull requests in approximately 10.9 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 71.6 places WayfireWM/wayfire in the S tier.
The external contributor pull request merge rate for WayfireWM/wayfire is 88.9%, based on public PR activity from non-core contributors.
WayfireWM/wayfire currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in WayfireWM/wayfire. Maintains strict focus on technical quality and test standards.
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/WayfireWM/wayfire?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (96% approval). Large PRs (>500 lines) take ~52 hours (40% approval). Keep your diff compact for rapid review.
Describe the feature The zoom feature follows the cursor by default. There is no option to avoid that. Benefits The main advantage is to be able to work on a specific area of the screen and then being able to move the cursor around to do precise work (text editing, design, gaming(?), ...) without making other valuable elements going out of focus.
Describe the issue When the lock screen program crashes, an explosion image pops up, and supposedly nothing works until restarting the lock screen program. This image does not provide any information about what just happened or why it happened, and therefore confuses the user to no end. Additional information Despite being given the opportunity to show text, the author of the session lock plugin decided to only show an explosion emoji: https://github.com/WayfireWM/wayfire/blob/master/plugins/protocols/session-lock.cpp#L190-L193 Related: #2911, #2998
Wayfire version 0.11.0-31beef5 (Feb 21 2026) branch main wlroots-0.19.2 GPU / Driver deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU deviceName = AMD Radeon RX 9060 XT (RADV GFX1200) driverID = DRIVER_ID_MESA_RADV driverName = radv driverInfo = Mesa 26.1.0-devel (git-f71a38e9de) Describe the bug Pixel movement can feel jumpy, often tied to the game's region. This stutter is most noticeable during movement. In Gles2, the bug is worse. With the Vulkan renderer, it's more noticeable when starting wf-recorder, but even without it, the bug is sometimes apparent. To Reproduce Playing games is the only way for now Screenshots / Videos / Stacktrace fullscreen for a better view. Wayfire wayfire-gaming.mp4 Niri niri-gaming.mp4
Currently, to include config.h in the public API headers, we need a check whether we are in Wayfire's own repo (where the path to the file is simply config.h), or whether we are being used from an external plugin, where we need to use wayfire/config.h instead. Since this is duplicated in multiple headers, it would probably make sense to add a common header file which can work in both cases, and contains the check.
Wayfire version 0.11.0-3c9a7712 (Jan 18 2026) branch master wlroots-0.19.2 Describe the bug Wayfire is allowing the alpha value to be set higher than 1.0. To Reproduce from wayfire import WayfireSocket sock = WayfireSocket() focused_view_id = sock.get_focused_view()["id"] sock.set_view_alpha(focused_view_id, 100.0) Expected behavior 1.0 max value
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 WayfireWM/wayfire, 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 WayfireWM/wayfire acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.9% were successfully merged into the primary branch.
WayfireWM/wayfire has a recorded first-timer success rate of 83.3%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 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 71.6 places WayfireWM/wayfire in the Elite tier.
The external pull request merge rate is 88.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, WayfireWM/wayfire currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for WayfireWM/wayfire 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.