A Python compiler design toolkit.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 82%
Response Time: 8d
First Timer Success: 77%
xdslproject/xdsl has a recorded first-timer success rate of 76.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in xdslproject/xdsl respond to incoming external pull requests in approximately 190.6 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 58.8 places xdslproject/xdsl in the A tier.
The external contributor pull request merge rate for xdslproject/xdsl is 81.7%, based on public PR activity from non-core contributors.
xdslproject/xdsl currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Python project in xdslproject/xdsl 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/xdslproject/xdsl?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 10:00 to 14:00 UTC (10:00 - 14: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 ~124 hours (96% approval). Large PRs (>500 lines) take ~915 hours (37% 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 Python.
Treat Requirements Like Code
pygeoapi is a Python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.
A unified trading API with more than 100 crypto exchanges and prediction markets in JavaScript / TypeScript / Python / C# / PHP / Go / Java
Summary xDSL currently has limited tiling support compared with upstream MLIR. At the moment, xdsl can tile some simple linalg.generic ops, but mostly only for static-shape memrefs. The current implementation is structured as: OperandTileInfo.analyze: computes how each operand should be sliced. TilingPlan.analyze_generic_op: builds a tiling plan for one linalg.generic. _verify_generic_is_tileable: rejects unsupported cases. _build_tile_loops: builds the outer scf.for loops. _build_tiled_subview: builds memref.subview ops for tiled operands. tile_linalg_generic: main entry point. Calls the helper functions, creates the tiled linalg.generic. One note: memref.subview itself can handle dynamic offsets/sizes/strides, but the current Linalg tiling flow still rejects dynamic operand shapes and uses static integer tile sizes / loop bounds. Missing compared with upstream MLIR Linalg tiling is currently missing support for: tensor-based tiling dynamic shapes / dynamic tile sizes partial ti
We're currently missing: RUF001 - https://docs.astral.sh/ruff/rules/ambiguous-unicode-character-string RUF002 - https://docs.astral.sh/ruff/rules/ambiguous-unicode-character-docstring RUF003 - https://docs.astral.sh/ruff/rules/ambiguous-unicode-character-comment RUF005 - https://docs.astral.sh/ruff/rules/collection-literal-concatenation RUF007 - https://docs.astral.sh/ruff/rules/zip-instead-of-pairwise RUF012 - https://docs.astral.sh/ruff/rules/mutable-class-default RUF015 - https://docs.astral.sh/ruff/rules/unnecessary-iterable-allocation-for-first-element RUF018 - https://docs.astral.sh/ruff/rules/assignment-in-assert RUF033 - https://docs.astral.sh/ruff/rules/post-init-default RUF043 - https://docs.astral.sh/ruff/rules/pytest-raises-ambiguous-pattern Any of these would be great to do, ideally one PR per rule.
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 xdslproject/xdsl, 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 xdslproject/xdsl acknowledge new external contributions in approximately 7 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.7% were successfully merged into the primary branch.
xdslproject/xdsl has a recorded first-timer success rate of 76.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 58.8 places xdslproject/xdsl in the Welcoming tier.
The external pull request merge rate is 81.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, xdslproject/xdsl currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for xdslproject/xdsl 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.