Rules-based browser gateway and link redirector.
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
alyraffauf/switchyard 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 alyraffauf/switchyard respond to incoming external pull requests in approximately 0.0 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.6 places alyraffauf/switchyard in the B tier.
The external contributor pull request merge rate for alyraffauf/switchyard is 0.0%, based on public PR activity from non-core contributors.
alyraffauf/switchyard currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in alyraffauf/switchyard. Reviews community pull requests with focus on project quality.
Discussions in alyraffauf/switchyard 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/alyraffauf/switchyard?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Is there a way to start Switchyard in the background? Motivation Starting Switchyard takes some time (at least on my computer and using Flathub). There is a setting called Keep running in background which speeds up when calling Switchyard again (which is great!), but does not solve the long wait on the first start. If there were a commandline switch, which starts Switchyard in the background without showing the interface, I could add Switchyard to my start-up apps, so that it is already running in the background when I use it for the first time. Is this possible?
Firstly, if I have missed a feature or misconfigured my app or extension, please do let me know. This app is exactly what I needed to solve a problem and I'm looking to optimise it. I've got Firefox 152.0 installed on my Fedora system and the WebExtension correctly picks up my installed browsers in the button in the menu bar. My routing also works when I right-click a link and choose "Open in Switchyard". Ideally, it would be nice to intercept all links and have them managed by Switchyard. Possibly behind a configuration option because I know that's a bit of overhead. I wanted to open all docs.google.com links on Chrome and right-clicking is something I'll 100% forget to do every instance.
Thanks for developing this app. Please also make deb package.
The browser icons in the launcher window are quite large (128x128px hardcoded in window_launcher.go). On lower resolution or smaller displays, this makes the launcher feel oversized. It would be helpful to have a configurable icon size, either: A icon_size setting in config.toml (e.g., icon_size = 64) Or a set of presets (small/medium/large) Currently the size is set via SetSizeRequest(128, 128) on the icon container and loadBrowserIcon(b, 128), so external CSS overrides don't take effect.
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 alyraffauf/switchyard, 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 alyraffauf/switchyard acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
alyraffauf/switchyard 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 ~-. 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.6 places alyraffauf/switchyard in the Solid tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, alyraffauf/switchyard 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 alyraffauf/switchyard 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.