gazebosim/gz-sim - Open Source PR Review Scorecard

Open source robotics simulator. The latest version of Gazebo.

C-Rank Grade: A (Welcoming) - 64/100

External PR Merge Rate: 54%

Response Time: -

First Timer Success: 52%

Frequently Asked Questions

Is gazebosim/gz-sim welcoming to first-time open-source contributors?

gazebosim/gz-sim has a recorded first-timer success rate of 52.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in gazebosim/gz-sim 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.

What does the 63.6 C-Rank™ score (A Tier) represent?

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 63.6 places gazebosim/gz-sim in the A tier.

What is the external contributor pull request merge rate for gazebosim/gz-sim?

The external contributor pull request merge rate for gazebosim/gz-sim is 53.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in gazebosim/gz-sim?

gazebosim/gz-sim currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

gazebosim
gazebosim/gz-simA•Welcoming1.5k
GitHub
Back to Explorer
gazebosim

gazebosim/gz-sim

1,540
InactiveA•Welcoming(64/100)C++

Open source robotics simulator. The latest version of Gazebo.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
5.8/10
Patience Score
6.6/10
Nitpick Rate
54%

Rigorous architecture standards (83% critical review signals). Ensure PRs strictly follow guidelines before requesting review in gazebosim/gz-sim.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
53.6%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
52.4%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
35 core
Highly collaborative maintainer core
Diagnostic Health HUD
53.6%
Merge Gauge
52.4%
1st-Timer
Community Vibe37/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for gazebosim/gz-sim
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/gazebosim/gz-sim)](https://getmerged.abhishekco.de/gazebosim/gz-sim?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Environment Ubuntu 24.04 Gazebo Sim 8.11.0 (Harmonic) Steps to reproduce Launch an empty world: gz sim empty.sdf Open the Resource Spawner plugin. Search for the official Open Robotics Spectrum Plane model. Download the model. Click Spawn. Expected behavior The model is inserted into the world. Actual behavior The model is not spawned. The console reports: Error [Utils.cc:176] Tried to use callback in sdf::findFile(), but the callback is empty. Did you call sdf::setFindCallback()? Additional observations I tested several official Fuel models using the same workflow: ✅ Breakfast Menu Original ✅ Construction Barrel ✅ Coke Can ✅ Office Chair ✅ Pioneer3AT (spawns, but reports a missing libSkidSteerDrivePlugin.so) ❌ Spectrum Plane (does not spawn) This appears to be specific to the Spectrum Plane model or its interaction with the Resource Spawner, rather than a general Resource Spawner failure.

📅 Opened Jul 1, 2026💬 1 comment
Quality: 40/100Contribute

We have utility functions here for converting an entity to a string for visualization reasons. This function in turn is called from scopedName that is used widely in the codebase, including in hot loops (such as updating collisions in physics, which for every contact point in every mesh in every simulation step calls the function twice gz-sim/src/systems/physics/Physics.cc Lines 4552 to 4555 in 63b0440 contactMsg->mutable_collision1()->set_name( removeParentScope(scopedName(_collEntity1, _ecm, "::", 0), "::")); contactMsg->mutable_collision2()->set_name( removeParentScope(scopedName(collEntity2, _ecm, "::", 0), "::")); ). The function itself performs fairly poorly, it's a long chain of if statements that try to fetch a component which requires itse

📅 Opened Jun 4, 2026💬 4 comments
Quality: 30/100Contribute

Desired behavior As noted in gazebo-tooling/release-tools#1490, there are tests in gz-sim that are being skipped on macOS due to a missing display. However, we should still build these tests to catch potential compile errors. For example, I ran into a build error on gz-sim8 on macOS that's not caught by CI since reset_sensors.cc is never compiled on that platform. There's a fix for it in #3000, but it was not backported to gz-sim8. Alternatives considered None Implementation suggestion Instead of appending tests that need display to gtest_source, we can accumulate a separate list and call gz_build_tests on them. We can then obtain the list of test targets from gz_build_tests and call set_test_properties and set the DISABLED property on them.

📅 Opened Apr 28, 2026💬 1 comment
Quality: 30/100Contribute

Description Currently, when defining an <actor> element in SDF using skeletal animations (such as .dae or .bvh files), the <scale> tag is ignored or only applies to the skin mesh, leading to broken visual rigging. Because the bone translations are hardcoded in absolute values within the animation file, resizing an actor dynamically via SDF is impossible without manually re-rigging the files in external software like Blender. Motivation and Use Case In the context of Digital Twins and autonomous vehicle simulations (Sim-to-Real), having dynamic environments with crowds is crucial. We need to generate pedestrians of various sizes (e.g., adults and children) using the same base 3D models and animation files to keep the simulation modular and lightweight. The current lack of scaling support forces developers to maintain multiple versions of the same .dae files at different scales, which goes against the modular philosophy of SDF. Proposed Solution When the parsing engine reads a <scale>X</

📅 Opened Mar 27, 2026💬 1 comment
Quality: 30/100Contribute

Environment OS Version: Ubuntu 24.04, macOS Source or binary build? source build of main branch Description Doxygen checks are enabled in CI in #3157, but there are many existing warnings that need to be fixed. Expected behavior: make doc can be run without doxygen warnings Actual behavior: There are many warnings (see CI logs for #3157) Steps to reproduce Check out branch for #3157 from source Run cmake and make doc Check contents of gz-doxygen.warn Output Excluding errors containing Detected potential recursive class relation between class and @param is not found in the argument list of Q_DECLARE_METATYPE(ComponentTypeId): Details 2026-03-07T23:07:24.6682429Z /github/workspace/src/gui/plugins/modules/EntityContextMenu.hh:43: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon) ... 2026-03-07T23:07:24.7120893Z /github/workspace/tutorials/resources.md:1: warning: multiple use of section label 'resources', (first occurre

📅 Opened Mar 7, 2026💬 11 comments
Quality: 45/100Contribute
Looking for more C++ beginner tasks?Explore C++ GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for gazebosim/gz-sim

When evaluating whether to contribute to gazebosim/gz-sim, 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 gazebosim/gz-sim acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 53.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to gazebosim/gz-sim

01

Is gazebosim/gz-sim welcoming to first-time open-source contributors?

gazebosim/gz-sim has a recorded first-timer success rate of 52.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 63.6 C-Rank™ score represent?

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 63.6 places gazebosim/gz-sim in the Welcoming tier.

04

What is the external contributor pull request merge rate for gazebosim/gz-sim?

The external pull request merge rate is 53.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in gazebosim/gz-sim?

Yes, gazebosim/gz-sim currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for gazebosim/gz-sim 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.