The modern Flyout app for Windows 11, built with Fluent 2 Design principles. Media Flyouts, Taskbar Widgets and more.
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 60%
Response Time: 1d
First Timer Success: 50%
unchihugo/FluentFlyout has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in unchihugo/FluentFlyout respond to incoming external pull requests in approximately 26.8 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 60.7 places unchihugo/FluentFlyout in the A tier.
The external contributor pull request merge rate for unchihugo/FluentFlyout is 59.7%, based on public PR activity from non-core contributors.
unchihugo/FluentFlyout currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in unchihugo/FluentFlyout. 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/unchihugo/FluentFlyout?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (75% approval). Large PRs (>500 lines) take ~129 hours (27% approval). Keep your diff compact for rapid review.
Description FluentFlyout setting's about page's open source licenses section is outdated: We removed WPF-UI 4.3.0 and replaced it with unchihugo.WPF-UI 4.4.1. This should be an easy change in the file FluentFlyoutWPF/ViewModels/AboutViewModel.cs. Open for new contributors looking to help with the project. Additional context No response Confirm that you have done the following: I have searched that there is no existing issue regarding my feature request I have read the FAQ and there is no answer to my feature request
Confirm that you have done the following: I have searched that there is no existing issue regarding my bug I have read the FAQ and there is no answer to my issue Describe the bug Minor annoyance. I'm closing the 'Premium features unlocked. Thank you for your support!' banner everywhere I find it, but it keeps coming back as soon as I switch back to that section. If it's supposed to stay there, then at least it should not have the X button. But it would be nice to be able to hide it for good. To Reproduce Pay for Premium Appreciate thank you banner, very considerate :) Close banner Navigate away from section or close FF Open FF / Navigate back to any of the premium sections. The banner is back Feeling very thanked, but slightly annoyed I cannot get rid of it :) ... Logs, screenshots & additional context No response Desktop Windows 11 FluentFlyout version: 2.9.2.0
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 unchihugo/FluentFlyout, 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 unchihugo/FluentFlyout acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 59.7% were successfully merged into the primary branch.
unchihugo/FluentFlyout has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 60.7 places unchihugo/FluentFlyout in the Welcoming tier.
The external pull request merge rate is 59.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, unchihugo/FluentFlyout currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for unchihugo/FluentFlyout 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.