An intuitive and customizable cross-platform ground control station for remote vehicles of all types.
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 65%
Response Time: 3h
First Timer Success: 25%
bluerobotics/cockpit has a recorded first-timer success rate of 25.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bluerobotics/cockpit respond to incoming external pull requests in approximately 2.5 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 72.2 places bluerobotics/cockpit in the S tier.
The external contributor pull request merge rate for bluerobotics/cockpit is 65.4%, based on public PR activity from non-core contributors.
bluerobotics/cockpit currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
An intuitive and customizable cross-platform ground control station for remote vehicles of all types.
Active maintainer team in bluerobotics/cockpit 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/bluerobotics/cockpit?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (82% approval). Large PRs (>500 lines) take ~12 hours (29% approval). Keep your diff compact for rapid review.
Some recent user feedback reminded me that #450 got implemented without support for logo images, which is necessary for some users for branding purposes. Copying relevant comments from the initial issue: ... there is an online converter of SVG files to the ass format drawing commands, although it may be worth rolling our own, or at least including options for scaling and a position offset. It could also be valuable to make/recommend a raster -> vector image converter that's focused on logos, since that's what we're expecting people to want to display, and users may not have a nice vector source already. It could be cool to have an optional Cockpit logo in the top right corner, and possibly also logo options for the autopilot firmwares (e.g. ArduSub, ArduPilot, PX4, etc) This may be technically possible already via a janky workaround of pasting the relevant ass drawing commands into a data lake variable, but that's not nicely exposed to users, and would require lots of manual trial
Current behaviour The context menu is linear, and option ordering is not aligned with expected relative usage, so there's a fair amount of unnecessary movement required to select a desired option, and it needs to be vertically precise. Expected or desired behaviour Make the menu radial (like in Houdini?), to minimise movement required to get to each option, and support gestures (like in Fusion360?), so power users are less distracted by UI elements they don't need to see: Prerequisites I have checked to make sure that a similar request has not already been filed or fixed.
As suggested by @ES-Alexander if we expect images to be all in the same format (just moved to AVIF), we should add notes in the development guide as well as put a validator in the CI. The only exceptions should be the images in the public folder, in special the PWA icons, as they need to be in this format for compatibility.
I assume we're wanting to avoid breaking other BlueOS Storage IDs, so maybe cockpit- should be an automatically applied prefix inside the useBlueOsStorage function instead? It seems unnecessary for Cockpit developers to need to write "cockpit" in lots of code locations whenever there's interaction with external systems 🤷♂️ Originally posted by @ES-Alexander in #2411 (review)
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 bluerobotics/cockpit, 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 bluerobotics/cockpit acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.4% were successfully merged into the primary branch.
bluerobotics/cockpit has a recorded first-timer success rate of 25.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 72.2 places bluerobotics/cockpit in the Elite tier.
The external pull request merge rate is 65.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, bluerobotics/cockpit currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for bluerobotics/cockpit 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.