Universal Robots ROS2 driver supporting CB3 and e-Series
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 80%
Response Time: 1d
First Timer Success: 100%
UniversalRobots/Universal_Robots_ROS2_Driver has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in UniversalRobots/Universal_Robots_ROS2_Driver respond to incoming external pull requests in approximately 33.4 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 59.9 places UniversalRobots/Universal_Robots_ROS2_Driver in the A tier.
The external contributor pull request merge rate for UniversalRobots/Universal_Robots_ROS2_Driver is 79.7%, based on public PR activity from non-core contributors.
UniversalRobots/Universal_Robots_ROS2_Driver currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in UniversalRobots/Universal_Robots_ROS2_Driver. Maintains strict focus on technical quality and test standards.
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/UniversalRobots/Universal_Robots_ROS2_Driver?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~22 hours (96% approval). Large PRs (>500 lines) take ~160 hours (36% approval). Keep your diff compact for rapid review.
Feature summary We could publish the current control mode as received by the primary interface. It is available in the RobotModeData message already. Related issues Links to related issues internal or external to this repo Tasks To complete this issue involves Implement the feature Make documentation Make Unit test Make example Test on real hardware
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 UniversalRobots/Universal_Robots_ROS2_Driver, 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 UniversalRobots/Universal_Robots_ROS2_Driver acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.7% were successfully merged into the primary branch.
UniversalRobots/Universal_Robots_ROS2_Driver has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 59.9 places UniversalRobots/Universal_Robots_ROS2_Driver in the Welcoming tier.
The external pull request merge rate is 79.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, UniversalRobots/Universal_Robots_ROS2_Driver currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for UniversalRobots/Universal_Robots_ROS2_Driver 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.