sktime/skpro
A unified framework for tabular probabilistic regression, time-to-event prediction, and probability distributions in python
In plain words
Outside PRs: 9 in 10 merged. First reply usually within 5.1 days. Replies slowed down this month.
Outside PRs merged
95%
18 merged, 1 closed, 5 still open
Higher than 79% of 565 other measured repositories
Merged (18)
#1139#1130#1126#1125#1124#1123#1122#1116#1114#1106#1104#1101#1094#1093#1092#1081#1078#1075
Closed without merging (1)
First human reply
5.1 days
median of 24 outside PRs, 0 unanswered
Time to merge
10 days
18 of 24 outside PRs merged
Outside PRs opened 30 to 120 days ago, so each has had time to be answered. A figure needs at least 5 pull requests, otherwise it reads "Not enough data". How this is calculated · A number looks wrong?
Your first steps here
If you have never contributed to this project, do these in order.
- 1
Read the contributing guide
It says how to set the project up and what the maintainers expect in a pull request.
Open the guide - 2
Find something small
No first issue is free right now. Look for a typo, a missing test or an unclear error message, or ask where help is wanted.
Browse open issues - 3
Know where to ask
Questions go to the project's discord, or on the issue itself. Not in private messages.
Open it - 4
Open a small pull request
Link the issue in it. A first reply here usually takes 5.1 days; until then, silence is normal.
What happens to an outside pull request
Every pull request opened by someone outside the core team, 30 to 120 days ago.
- Opened by outsiders24100%
- Got a human reply24100%
- Merged1875%
Time to first reply
After 2 days, 33% of outside PRs had a reply from a person. After a week, 54%. Bots do not count.
The last 52 weeks
Slowed down. Median first reply was Not enough data over the last four weeks (41 PRs) and 4.7 days over the four before (9 PRs).
Starter issues
Issues labelled for beginners, with their real state. Available means open, unassigned, no linked pull request, nobody has claimed it in the last 14 days, and it was updated in the last 60 days.
- Available
- 0
- Claimed
- 0
- Has a pull request
- 17
- Stale
- 2
- Has a pull request[ENH] add `tests:specific` mechanism for VM-based running of estimator specific tests#1164
- Has a pull request[ENH] add at least one usage example to docstrings of estimators#1135
- Has a pull request[DOC] add explicit formulae to docstrings of distributions#1120
When replies arrive
All maintainers counted together. Shown only when at least 3 people replied in the last 90 days, so it never describes one person.
Replies are most likely between 17:00 and 20:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 2 |
| 01:00 | 5 |
| 02:00 | 7 |
| 03:00 | 2 |
| 04:00 | 1 |
| 05:00 | 1 |
| 06:00 | 1 |
| 07:00 | 0 |
| 08:00 | 0 |
| 09:00 | 0 |
| 10:00 | 0 |
| 11:00 | 0 |
| 12:00 | 0 |
| 13:00 | 0 |
| 14:00 | 0 |
| 15:00 | 1 |
| 16:00 | 1 |
| 17:00 | 5 |
| 18:00 | 7 |
| 19:00 | 3 |
| 20:00 | 4 |
| 21:00 | 6 |
| 22:00 | 4 |
| 23:00 | 4 |
How to start
- Contributing guidefound
- Code of conductfound
- Issue templatesfound
- Dev container for one-step setupnot found
- No CLA or sign-off requirement was found.
Where the project talks
Activity
- Commits, 90 days
- 46
- Releases, 12 months
- 7
- Active maintainers
- 4
- Last push
- 9 Oct 2026
Stack
Similar repositories
Same main language (Python), most shared frameworks and topics first, then the faster reply.
SunPy - Python for Solar Physics
- First reply
- 4 h
- 36 outside PRs