:mag: Quick file search & app launcher for Windows with community-made plugins
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 62%
Response Time: 2d
First Timer Success: 38%
Flow-Launcher/Flow.Launcher has a recorded first-timer success rate of 37.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Flow-Launcher/Flow.Launcher respond to incoming external pull requests in approximately 53.2 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 59.3 places Flow-Launcher/Flow.Launcher in the A tier.
The external contributor pull request merge rate for Flow-Launcher/Flow.Launcher is 61.9%, based on public PR activity from non-core contributors.
Flow-Launcher/Flow.Launcher 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 Flow-Launcher/Flow.Launcher. 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/Flow-Launcher/Flow.Launcher?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~35 hours (77% approval). Large PRs (>500 lines) take ~255 hours (28% approval). Keep your diff compact for rapid review.
Checks I have checked that this issue has not already been reported. I am using the latest version of Flow Launcher. I am using the prerelease version of Flow Launcher. Problem Description When two plugins use the same dependency but with different versions, it can break one of the plugins. This seems to be due to two DLLs being loaded and in my specific case it seems to try to cast a matching class between the different dependency versions and crash. This issue was first reported on my plugin AppAudioManger here: DavidGBrett/Flow.Launcher.Plugin.AppAudioManager#8 by @Jack251970 The other conflicting plugin was AudioDeviceSelector: https://github.com/attilakapostyak/Flow.Launcher.Plugin.AudioDeviceSelector In this case my plugin was using NAudio version 2.2.1, while AudioDeviceSelector was using 2.1.0 From my brief research, you may be able to fix this by isolating the plugins / their dependencies using: System.Runtime.Loader.AssemblyLoadContext Though I don't know enough ab
Checks I have checked that this issue has not already been reported. I am using the latest version of Flow Launcher. I am using the prerelease version of Flow Launcher. Problem Description I switched from Listary to Flow Launcher after Flow supported Dialog Jumps. Sadly, the feature works only on "Open" file dialog. On "Save as" dialogs: Flow Launcher shows itself behind the dialog windows → ✅ File Search (via Everything) works → ✅ Clicking the result or press Enter does nothing but select and focus the filename field in file dialog → ❌ Tested on following programs: PDF XChange Editor Vivaldi Paint.Net Edge To Reproduce Enable Dialog Jump option in Flow Launcher Open any file in any program Perform a "Save as..." to open file dialog Try to go to a searched path in Flow Launcher Screenshots No response Flow Launcher Version 2.0.3 Windows Build Number Windows 11 25H2 26200.7623 Error Log Details 10:58:25.1417+01:00 - ERROR - DialogJump.DirJump - Failed to jum
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 Flow-Launcher/Flow.Launcher, 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 Flow-Launcher/Flow.Launcher acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.9% were successfully merged into the primary branch.
Flow-Launcher/Flow.Launcher has a recorded first-timer success rate of 37.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 59.3 places Flow-Launcher/Flow.Launcher in the Welcoming tier.
The external pull request merge rate is 61.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Flow-Launcher/Flow.Launcher 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 Flow-Launcher/Flow.Launcher 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.