An open source web application for railway infrastructure design, capacity analysis, timetabling and simulation
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 81%
Response Time: 1d
First Timer Success: 78%
OpenRailAssociation/osrd has a recorded first-timer success rate of 78.3%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in OpenRailAssociation/osrd respond to incoming external pull requests in approximately 29.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 74.5 places OpenRailAssociation/osrd in the S tier.
The external contributor pull request merge rate for OpenRailAssociation/osrd is 80.5%, based on public PR activity from non-core contributors.
OpenRailAssociation/osrd currently has 17 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
An open source web application for railway infrastructure design, capacity analysis, timetabling and simulation
Strict review standards in OpenRailAssociation/osrd. Ensure PR scope matches issue requirements closely before requesting review.
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/OpenRailAssociation/osrd?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~19 hours (96% approval). Large PRs (>500 lines) take ~139 hours (36% approval). Keep your diff compact for rapid review.
What happened? we don't use the open data sncf since the new itinerary modal is set up. we should remove it from our data sources: What did you expect to happen? No response How can we reproduce it (as minimally and precisely as possible)? go to "about" see On which environments the bug occurs? No response On which browser the bug occurs? No response OSRD version (top right corner Account button > Informations) staging 49bca16
What happened? When a train is non-simulated, margin can be computed too (currently only %, but soon min/100km too). The margin is then distributed linearly, but MARECO is still available, it should not. What did you expect to happen? Disable the MARECO margin for non-simulated trains. How can we reproduce it (as minimally and precisely as possible)? create train with no RS On which environments the bug occurs? Dev (SNCF) On which browser the bug occurs? Firefox OSRD version (top right corner Account button > Informations) dev 69435ec
What happened? (for non-simulated trains) When clearing either the requested arrival time or the requested base arrival time, the other one is cleared at the same time. What did you expect to happen? Both fields should be independant, clearing one should not affect the other. How can we reproduce it (as minimally and precisely as possible)? video On which environments the bug occurs? Dev (SNCF) On which browser the bug occurs? Firefox OSRD version (top right corner Account button > Informations) dev 69435ec
What happened? It is possible to set a power restriction on the last step, but power restriction are range-data (so starting at that point). So there is no point in setting this field. And it's most of the time cleaned-up in other interactions (like adding a power restriction at previous stop). What did you expect to happen? No input/no interaction possible at this field (grey-out field if consistent with UX) How can we reproduce it (as minimally and precisely as possible)? Create a train in a scenario select a RS with power restrictions (like 1TGVDUPL) provide power restrictions on the last step in time-table On which environments the bug occurs? Recette (SNCF) On which browser the bug occurs? Firefox OSRD version (top right corner Account button > Informations) bebf2a8
What happened? Long secondary codes are cropped at a few places. I. In the STD II. In the waypoints panel Note that there are 2 scrolling bars, which is not ideal. 1: the secondary code is displayed, but require scrolling with 2. to be readable. 2: horizontal scroll bar, should be avoided, or only present when no space is left between OP name and OP secondary code. 3: vertical scroll bar, I guess this is just a css bug, this should be removed. III. In the train schedule sheet What did you expect to happen? I. Push the text to the left if there is enough space or ellipsis. Ideally provide a tooltip showing the full text. II. Push the text (so the column) to the left or ellipsis if no more space. Remove the vertical scroll bar. III. Push the text to the left if there is enough space or ellipsis. Ideally provide a tooltip showing the full text. How can we reproduce it (as minimally and precisely as possible)? Based on this infra: France_OSM (see internal here: https://sncf.sharepoint.c
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 OpenRailAssociation/osrd, 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 OpenRailAssociation/osrd acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.5% were successfully merged into the primary branch.
OpenRailAssociation/osrd has a recorded first-timer success rate of 78.3%. Repositories ranked Elite 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 74.5 places OpenRailAssociation/osrd in the Elite tier.
The external pull request merge rate is 80.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, OpenRailAssociation/osrd currently has 17 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for OpenRailAssociation/osrd 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.