MobiFlight is an open source project that allows you to create your own home cockpit for your favorite flight simulator in a flexible, affordable and extremely user-friendly way.
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 85%
Response Time: 22h
First Timer Success: 69%
MobiFlight/MobiFlight-Connector has a recorded first-timer success rate of 69.2%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in MobiFlight/MobiFlight-Connector respond to incoming external pull requests in approximately 22.1 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 70.5 places MobiFlight/MobiFlight-Connector in the S tier.
The external contributor pull request merge rate for MobiFlight/MobiFlight-Connector is 85.2%, based on public PR activity from non-core contributors.
MobiFlight/MobiFlight-Connector currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in MobiFlight/MobiFlight-Connector. Ensure PR scope matches issue requirements closely before requesting review.
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/MobiFlight/MobiFlight-Connector?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (96% approval). Large PRs (>500 lines) take ~106 hours (38% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in C#.
Practical generic programming for .NET
A .NET indexing and search engine powered by Lucene.Net
A cross-platform UI framework for .NET.
Describe the bug The log entries for 7 segment displays shows only one space character as data even if multiple spaces are send. Most likely this happens also for other devices like LCD displays. Steps To Reproduce Steps to reproduce the behavior: activate log send a value to 7 segement display clear the display the log shows only one space for the data send Expected behavior For the 7 segment displays the log should show 8 spaces for clearing the display Actual behavior see above Details MobiFlight Version: 11.x.y FlightSim: all AddOn: all Additional context n/a
Is your feature request related to a problem? Please describe. We would like to honor our gold sponsors and create an extra incentive for supporting mobiFlight. Describe the solution you'd like Show the logos of our gold sponsors (highest tier) on the splash screen.
Is your feature request related to a problem? Please describe. If you try to quit MobiFlight with unsaved changes, MobiFlight asks if you want to save your profile. This question has different context that what the user is trying to do. If you choose "no" you will quit without saving. This can catch you off guard, as your mind is focused on closing the app, realize you didn't save, and accidentally choosing "no" (to not quit) which is exactly not what you want. Describe the solution you'd like I would like to play safe and make the question explicitly about quit without changing context to saving the profile, so "no" means "no, do not continue", and backing off is the safe choice. "You have unsaved changes, are you sure you want to quit?" Describe alternatives you've considered Eventually we might want to change to a model where changes are saved instantly, and changes can be reverted with undo. But this is is a separate discussion altogether and out of scope here.
Describe the bug When you create a new output config item while in run mode, a lot of error messages are created in the log Steps To Reproduce Steps to reproduce the behavior: Open project in MobiFlight Run MobiFlight Create new Output Config See error Expected behavior No log messages Actual behavior Error log messages. Details MobiFlight Version: 11.1.0.x
Describe the bug We have several categories with spelling errors or other types of inconsistencies. Lets collect a list of cases and correct them via database updates. List of buggy categories Vendor Asobo / Microsoft -> decide on one and only use one ✅ vskylabs -> move to xplane ✅ FlightSim Studio / FSS -> merge into one "FlightSim Studio (FSS)" ✅ Microsoft/Carenado -> Carenado ✅ Mobiflight -> remove ✅ All vendors / All aircraft -> Microsoft.Generic ✅ Aircraft Generic -> Rename to something like "All aircraft" / "All planes" / "Standard planes" System A2A / Comanche 250 / Flight Intrumentation (spelling) Air Condition / Pressurization :white: -> Air Condition & Pressurization :white: Air Conditioning / Pressurisation / Ventilation -> Air Condition & Pressurization :white: Air Condition and Pressurization -> Air Condition & Pressurization :white: Air Condition / Pressurization -> Air Condition & Pressurization :white: Air Conditioning -> Air Condition & Pressurization :wh
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 MobiFlight/MobiFlight-Connector, 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 MobiFlight/MobiFlight-Connector acknowledge new external contributions in approximately 22 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.2% were successfully merged into the primary branch.
MobiFlight/MobiFlight-Connector has a recorded first-timer success rate of 69.2%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~22 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 70.5 places MobiFlight/MobiFlight-Connector in the Elite tier.
The external pull request merge rate is 85.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, MobiFlight/MobiFlight-Connector currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for MobiFlight/MobiFlight-Connector 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.