OpenROAD's unified application implementing an RTL-to-GDS Flow. Documentation at https://openroad.readthedocs.io/en/latest/
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 59%
Response Time: -
First Timer Success: 65%
The-OpenROAD-Project/OpenROAD has a recorded first-timer success rate of 65.2%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in The-OpenROAD-Project/OpenROAD 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 67.1 places The-OpenROAD-Project/OpenROAD in the A tier.
The external contributor pull request merge rate for The-OpenROAD-Project/OpenROAD is 59.5%, based on public PR activity from non-core contributors.
The-OpenROAD-Project/OpenROAD currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in The-OpenROAD-Project/OpenROAD 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/The-OpenROAD-Project/OpenROAD?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (74% approval). Large PRs (>500 lines) take ~115 hours (27% approval). Keep your diff compact for rapid review.
We should include logger_->metric() for some relevant metrics, this allows for having them available in the dashboard for evaluations. For example, these final values, which are only available in the log files, not json currently: [INFO GPL-1001] Global placement finished at iteration 2047 [INFO GPL-1017] Routability mode iteration count: 1604 [INFO GPL-1005] Routability final weighted congestion: 1.1051 [INFO GPL-1011] Original area (um^2): 26000.50 [INFO GPL-1012] Total routability artificial inflation: 1284.63 (+4.94%) [INFO GPL-1013] Total timing-driven delta area: 8451.95 (+32.51%) [INFO GPL-1014] Final placement area: 35737.08 (+37.45%) [INFO GPL-1018] Final HPWL (um): 694084.76 Easy to implement, we just need a logger_->metric() for each with a proper naming.
Description The previous issue #10749 and PR #10769 had some tests which were not yet isolated. aberndt@dev-secure-augusto:~/workspace/masterCode/tools/OpenROAD/src$ grep -rin detailed_placement cts/test/array_dummy.tcl:147:detailed_placement cts/test/array_full_flow.tcl:146:detailed_placement cts/test/array_no_blockages.tcl:145:detailed_placement cts/test/array_max_wl.tcl:147:detailed_placement cts/test/array.tcl:148:detailed_placement cts/test/array_repair_clock_nets.tcl:149:detailed_placement cts/test/array_ins_delay.tcl:146:detailed_placement The PR #11089 required updating some of those, we would not need to update them if CTS tests were all isolated. Suggested Solution We should remove DPL and GPL calls from CTS regression tests. We should generate a DEF file including the output of tools other than CTS commands, replacing the necessity of the exterior commands. Additional Context No response
Description This is a public tracker for feature development for the ram tool. Add support for endcap insertion Endcaps need to be inserted around the perimeter of the RAM bounding box after fill Physical verification Check that timing, LVS, and DRC are clean via external tools Sweep word and bit sizes 1-64 (all values) to verify support for arbitrary array sizes (no placement or routing errors, LVS clean, DRC clean, passes STA) Add support for AND3/AND4 cells in the decoder Only AND2 is supported now. Larger arrays can be more efficient with wider ANDs Add support for automatic master selection Find and identify FFs, ICGs, buffers, inverters, tristates, AND2/3/4s automatically if not user specified Automatic detection of the followpin metal layer and width The current implementation requires manual specification of the followpin layer and width. This should be automatically extractable from the library. The user should not need to specify this. Add support for
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 The-OpenROAD-Project/OpenROAD, 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 The-OpenROAD-Project/OpenROAD acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 59.5% were successfully merged into the primary branch.
The-OpenROAD-Project/OpenROAD has a recorded first-timer success rate of 65.2%. 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 67.1 places The-OpenROAD-Project/OpenROAD in the Welcoming tier.
The external pull request merge rate is 59.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, The-OpenROAD-Project/OpenROAD 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 The-OpenROAD-Project/OpenROAD 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.