An open source web application for railway infrastructure design, capacity analysis, timetabling and simulation
C-Rank Grade: A (Welcoming) - 70/100
External PR Merge Rate: 86%
Response Time: 2d
First Timer Success: 80%
OpenRailAssociation/osrd has a recorded first-timer success rate of 80.4%. Repositories ranked A 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 48.3 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 69.7 places OpenRailAssociation/osrd in the A tier.
The external contributor pull request merge rate for OpenRailAssociation/osrd is 85.8%, based on public PR activity from non-core contributors.
OpenRailAssociation/osrd currently has 15 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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~31 hours (96% approval). Large PRs (>500 lines) take ~232 hours (39% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in TypeScript.
Official Sentry SDKs for JavaScript
No repository description available.
orval is able to generate client with appropriate type-signatures (TypeScript) from any valid OpenAPI v3 or Swagger v2 specification, either in yaml or json formats. 🍺
Description and goal The test me_privileges in editoast/src/views/authz verify that the endpoint /authz/me/privileges returns all user privileges. In the test, no checks are done concerning rolling stock privileges. Acceptance criteria Add rolling stocks in the test The test must pass
Description and goal The endpoint is not tested. Add a few tests about its expected behavior and its authorization. Acceptance criteria Tests exist about: Its general behavior: what payloads it accepts and what it returns. Its authorization: which roles and grants are needed to use it without getting a 403 Forbidden response.
Description and goal The endpoint is not tested. Add a few tests about its expected behavior and its authorization. Acceptance criteria Tests exist about: Its general behavior: what payloads it accepts and what it returns. Its authorization: which roles and grants are needed to use it without getting a 403 Forbidden response.
What happened? I create several nodes I multiselect them (using right click + rectangle selection) I move them my using Ctrl + Mousewheel I refresh the page : the nodes came back to their previous position What did you expect to happen? I expect the new positions to be saved How can we reproduce it (as minimally and precisely as possible)? As above On which environments the bug occurs? Dev (SNCF) On which browser the bug occurs? Google Chrome OSRD version (top right corner Account button > Informations) 592a006
What happened? The rouding of the friction coefficients is excessive leading to display 0 kN for (almost?) every rolling stock. Also, kN is displayed but we use kN/t in the data. What did you expect to happen? We should keep 5 to 6 digits after the decimal point. We may want to decide what to display, kN or kN/t and adapt the frontend accordingly. This is actually the missing front part of osrd-project/osrd-confidential#1616 How can we reproduce it (as minimally and precisely as possible)? rolling stock editor select any rolling stock check friction coefficients On which environments the bug occurs? Dev (SNCF), Production (SNCF), Recette (SNCF), Integration (SNCF), Preproduction (SNCF) On which browser the bug occurs? Firefox OSRD version (top right corner Account button > Informations) v1.2.20 2d122ae
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 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.8% were successfully merged into the primary branch.
OpenRailAssociation/osrd has a recorded first-timer success rate of 80.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 69.7 places OpenRailAssociation/osrd in the Welcoming tier.
The external pull request merge rate is 85.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, OpenRailAssociation/osrd currently has 15 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.