sktime/skpro - Open Source PR Review Scorecard

A unified framework for tabular probabilistic regression, time-to-event prediction, and probability distributions in python

C-Rank Grade: A (Welcoming) - 63/100

External PR Merge Rate: 59%

Response Time: 16h

First Timer Success: 25%

Frequently Asked Questions

Is sktime/skpro welcoming to first-time open-source contributors?

sktime/skpro has a recorded first-timer success rate of 25.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in sktime/skpro respond to incoming external pull requests in approximately 15.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 63.2 C-Rank™ score (A Tier) represent?

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 63.2 places sktime/skpro in the A tier.

What is the external contributor pull request merge rate for sktime/skpro?

The external contributor pull request merge rate for sktime/skpro is 59.1%, based on public PR activity from non-core contributors.

Are there Good First Issues available in sktime/skpro?

sktime/skpro currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

sktime
sktime/skproA•Welcoming330
GitHub
Back to Explorer
sktime

sktime/skpro

330
InactiveA•Welcoming(63/100)Python

A unified framework for tabular probabilistic regression, time-to-event prediction, and probability distributions in python

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in sktime/skpro welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
15 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
59.1%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
25.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
8 core
Highly collaborative maintainer core
Diagnostic Health HUD
59.1%
Merge Gauge
25.0%
1st-Timer
Community Vibe49/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for sktime/skpro
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/sktime/skpro)](https://getmerged.abhishekco.de/sktime/skpro?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

In sktime, it is possible to specify modules that contain tests for a given estimator that should run in the VM-based test suite, if tests:vm is specified. This has not been added in skpro, we should upgrade the status of the skpro test and tag system to the state of sktime. For testing, we should add tests:specific tags populated at least for some of the estimators.

📅 Opened Sep 26, 2026💬 1 comment
Quality: 90/100Contribute

We should ensure that all scikit-base classes in skpro have at least one usage example. The recipe to find all those without: from sktime.registry import all_estimators [x for x in all_estimators() if ">>>" not in x.__doc__] Once the docstring is added, the _tags should be checked for the line "tests:skip_by_name": ["test_class_has_doctest_example"], which skips the test requiring a docstring. If present, this line should also be removed. Please post here which estimator/object you are working on before starting. If you find a bug with the estimator, e.g., unexpected failures, in the process of adding an example, please open a new issue. The recipe for adding examples is: add an example section in numpydoc stype use as template for a simple example: MultipleQuantileRegressor use as template for complex/multiple examples: NaiveProbaRegressor (search in code base) To pick this up, post an estimator here that you are working on, to avoid double work, and make a PR.

📅 Opened Sep 10, 2026💬 10 comments
Quality: 100/100Contribute

We should add, where known, explicit formulae to the docstrings of distribution methods. This is done by populating the _formula_docs attribute of the given distribution, see the extension template in extension_templates.distributions for a detail explanation, and Normal for an example of a populated distribution. Contributors can help by: adding formulae to a distribution which does not have them yet adding formulae for more methods in a distribution which already has them Please post here before starting, to avoid duplication: which distribution and method(s) you are working on. If opening a PR, please provide a reference for the formula - either a literature reference, or your own compitation. No AI generated formulae please, since these tend to be hallucinated. Recipe for finding distributions that have not yet been dealt with: from skpro.registry import all_objects all_dists = all_objects("distribution", return_names=False) dists_without_formula = [d for d in all_dists if not h

📅 Opened Aug 7, 2026💬 7 comments
Quality: 90/100Contribute

hyperactive has a tuner that can be used for skpro tuning with arbitrary hyperparameter optimization backend. However, it is not visible from the skpro documentation. This should be added using the same forwarding pattern as sktime Prophetverse. It may be that it is necessary to add the _placeholder_record to skpro for this.

📅 Opened May 17, 2026💬 4 comments
Quality: 70/100Contribute

Even though scikit-learn supports probabilistic classification and, thus, discrete output distributions, it has a few problems: the predict_proba API is inconsistent with the skpro regression API, as it returns a numpy array and not a distribution object there is no API for multivariate probabilistic classification, or ordinal regression. It was suggested by @felipeangelimvieira to add a skpro native probabilistic classifier API that can represent a wider range of return distributions. Someone working on this should give more details about the API design first. As a starting point, I suggest: a new module classification a base class BaseProbaClassifier with methods fit, predict and predict_proba if ordinal classification is also covered, then predict_quantiles and predict_interval may also make sense, in this case a capability tag for ordinal classification a distribution DiscreteClass used for the output a scikit-learn adapter that allows to expose any sklearn probabilistic classif

📅 Opened Mar 28, 2026💬 3 comments
Quality: 70/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for sktime/skpro

When evaluating whether to contribute to sktime/skpro, 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 sktime/skpro acknowledge new external contributions in approximately 15 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 59.1% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to sktime/skpro

01

Is sktime/skpro welcoming to first-time open-source contributors?

sktime/skpro has a recorded first-timer success rate of 25.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~15 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 63.2 C-Rank™ score represent?

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 63.2 places sktime/skpro in the Welcoming tier.

04

What is the external contributor pull request merge rate for sktime/skpro?

The external pull request merge rate is 59.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in sktime/skpro?

Yes, sktime/skpro currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for sktime/skpro 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.