NASA's aircraft analysis, design, and optimization tool
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 53%
Response Time: 9h
First Timer Success: 38%
OpenMDAO/Aviary 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 OpenMDAO/Aviary respond to incoming external pull requests in approximately 8.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 61.2 places OpenMDAO/Aviary in the A tier.
The external contributor pull request merge rate for OpenMDAO/Aviary is 52.9%, based on public PR activity from non-core contributors.
OpenMDAO/Aviary currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in OpenMDAO/Aviary welcoming community pull requests and bug fixes.
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/OpenMDAO/Aviary?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 Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (66% approval). Large PRs (>500 lines) take ~43 hours (24% approval). Keep your diff compact for rapid review.
Desired capability or behavior. The utility get_option_defaults() (in aviary.variable_info.options.py) which sets up an AviaryValues object with every variable set to their default units. This is often used to set up tests. This util makes the tests extremely annoying to debug because it makes it very opaque which inputs are being set that the component actually uses, and what value they are set to. The defaults are mostly zero anyway, and also add an unnecessary dependency for tests on default values in metadata. If a default is change, it shouldn't break every single test using that variable. TLDR: get_option_defaults() is a shortcut that obscures 1. what variables are actually necessary for a test, 2. their values, and 3. creates fragile dependencies for the tests on the current metadata defaults Suggested implementation. Update tests to not use get_option_defaults() and instead directly set input values for the OM problem. If there are no special cases where get_option_defaults() i
Desired capability or behavior. Currently these variables: Aircraft.CrewPayload.Design.NUM_SEATS_ABREAST_BUSINESS Aircraft.CrewPayload.Design.NUM_SEATS_ABREAST_ECONOMY Aircraft.CrewPayload.Design.NUM_SEATS_ABREAST_FIRST Aircraft.CrewPayload.Design.SEAT_PITCH_BUSINESS Aircraft.CrewPayload.Design.SEAT_PITCH_ECONOMY Aircraft.CrewPayload.Design.SEAT_PITCH_FIRST Are in a strange location in the hierarcy as they describe the aircraft configuration, not it's loading. Suggest we move them to Aircraft.Fuselage.NUM_SEATS_ABREAST_BUSINESS Aircraft.Fuselage.NUM_SEATS_ABREAST_ECONOMY Aircraft.Fuselage.NUM_SEATS_ABREAST_FIRST Aircraft.Fuselage.SEAT_PITCH_BUSINESS Aircraft.Fuselage.SEAT_PITCH_ECONOMY Aircraft.Fuselage.SEAT_PITCH_FIRST So that they sit alongside the SEAT_WIDTH variables. This issue should include a discussions on the following: Should we change Aircraft.CrewPayload.Design.NUM_BUSINESS_CLASS etc to be totals of the number of seats rather than the number of passengers on the 'design' m
Desired capability or behavior. Note from Jason: "this should be removed from metadata (intermediate calculation)". See note # 1182 in variable_info/variable_meta_data.py and subsystems/geometry/flops_based/characteristic_lengths.py. Suggested implementation. No response
Desired capability or behavior. Note from Jennifer: currently excluding Dynamic variables that do not have proper full names mirroring the hierarchy. The variables that are excluded are: Dynamic.Atmosphere.\*, Dynamic.Mission.\*, Dynamic.Vehicle.\* . Should dynamic variables be updated to match hierarchy names? See MetaDataTest.test_alphabetization() in variable_info/test/test_var_structure.py. Suggested implementation. No response
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 OpenMDAO/Aviary, 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 OpenMDAO/Aviary acknowledge new external contributions in approximately 8 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 52.9% were successfully merged into the primary branch.
OpenMDAO/Aviary 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 ~8 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 61.2 places OpenMDAO/Aviary in the Welcoming tier.
The external pull request merge rate is 52.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, OpenMDAO/Aviary 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 OpenMDAO/Aviary 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.