First-party plugins maintained by the Kedro team.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 57%
Response Time: 3h
First Timer Success: 75%
kedro-org/kedro-plugins has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kedro-org/kedro-plugins respond to incoming external pull requests in approximately 3.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 60.4 places kedro-org/kedro-plugins in the A tier.
The external contributor pull request merge rate for kedro-org/kedro-plugins is 57.1%, based on public PR activity from non-core contributors.
kedro-org/kedro-plugins currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in kedro-org/kedro-plugins. Prompt code reviews with positive guidance for new contributors.
Discussions in kedro-org/kedro-plugins focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/kedro-org/kedro-plugins?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (71% approval). Large PRs (>500 lines) take ~16 hours (26% approval). Keep your diff compact for rapid review.
Description Update docstrings to point out that filepath type is str | os.PathLike, not just str. For contributors: feel free to open a PR per dataset type for ease of review. Sub-tasks Do the above for all dataset groups: API Biosequence (#1336) Dask (#1332) Databricks Email (#1336) Geopandas (#1329) Holoviews (#1334) Huggingface Ibis (#1487) JSON (#1324) Langchain Matlab Matplotlib NetworkX OpenXML (#1331) Pandas Partitions (#1495) Pickle (#1324) Pillow Plotly Polars (#1330) Redis (#1496) Snowflake Spark (#1423) SVMLight TensorFlow (#1477) Text (#1324) YAML (#1324)
Description Testing that os.PathLike objects work and fix if needed. The unit tests currently cast paths to string, but the doctests getting included as part of kedro-org/kedro#2287 are probably doing a fair job of ensuring this. For contributors: feel free to open a PR per dataset type for ease of review. Sub-tasks Do the above for all dataset groups: To be done Dask Matplotlib Partitions (#1501) Completed (can use PRs as inspiration) API Biosequence (#1336) Holoviews (#1334) JSON (#1324) Pickle (#1324) Polars (#1337) Plotly (#1375) Text (#1324) YAML (#1324) SVMLight (#1471) Matlab (#1480) NetworkX (#1467) Pillow (#1443) Spark (#1423) Pandas (#1404) TensorFlow (#1477) OpenXML (#1478) (#1479) Ibis (#1487) Databricks Huggingface Langchain Snowflake Redis (#1496) Email (#1488) Geopandas (#1489)
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 kedro-org/kedro-plugins, 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 kedro-org/kedro-plugins acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.1% were successfully merged into the primary branch.
kedro-org/kedro-plugins has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 hours. 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 60.4 places kedro-org/kedro-plugins in the Welcoming tier.
The external pull request merge rate is 57.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kedro-org/kedro-plugins 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 kedro-org/kedro-plugins 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.