ArduPlane, ArduCopter, ArduRover, ArduSub source
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 48%
Response Time: -
First Timer Success: 35%
ArduPilot/ardupilot has a recorded first-timer success rate of 34.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ArduPilot/ardupilot 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 64.4 places ArduPilot/ardupilot in the A tier.
The external contributor pull request merge rate for ArduPilot/ardupilot is 48.2%, based on public PR activity from non-core contributors.
ArduPilot/ardupilot currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in ArduPilot/ardupilot. Prompt code reviews with positive guidance for new contributors.
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/ArduPilot/ardupilot?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (60% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
Bug Report Issue details The define cuts out the CPU-based spoolup blocking code where it shouldn't. see takeoff_check.cpp Version master Platform [ ] All [ ] AntennaTracker [x] Copter [ ] Plane [ ] Rover [ ] Submarine Airframe type all except heli Hardware type n/a Logs n/a
Feature Request As part of reviewing PR #32233 @peterbarker and @rmackay9 both thought that it would be best if this was moved to the Copter class. The means the code itself should be moved from RC_Channel_Copter to Copter.cpp (I think) This shouldn't be any change in behaviour but it should be at least lightly tested in SITL.
Feature request Is your feature request related to a problem? Please describe. If a vehicle goes too deep (e.g. beyond its component depth ratings), it can implode / get destroyed under the pressure. We don't currently have a means of directly warning about this before it starts happening. Describe the solution you'd like Make a dedicated external pressure failsafe, which monitors a baro specified as BARO_TYPE_WATER. That keeps setup, defaults, and user intuition simple, at the cost of some ambiguity around what to do if there is more than one water baro available (I vote just check the primary baro, and use it for the failsafe if it is a water baro). Ideally it would be a multi-level failsafe, with low and critical depths specified (like with battery voltage). I believe the most logical supported actions are "Warn only", and "Surface", but "Depth hold" could potentially be an option in between 🤷♂️ . Describe alternatives you've considered We could alternatively expand the cu
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 ArduPilot/ardupilot, 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 ArduPilot/ardupilot acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 48.2% were successfully merged into the primary branch.
ArduPilot/ardupilot has a recorded first-timer success rate of 34.6%. Repositories ranked Welcoming 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 64.4 places ArduPilot/ardupilot in the Welcoming tier.
The external pull request merge rate is 48.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ArduPilot/ardupilot currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ArduPilot/ardupilot 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.