jax-ml/jax
Composable transformations of Python+NumPy programs: differentiate, vectorize, JIT to GPU/TPU, and more
In plain words
Outside PRs: 7 in 10 merged. First reply usually within 7 days. Replies got faster this month.
Outside PRs merged
66%
122 merged, 62 closed, 98 still open
Higher than 21% of 565 other measured repositories
First human reply
7 days
median of 282 outside PRs, 100 unanswered
Time to merge
Not enough data
122 of 282 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
No chat was found. Ask on the issue you are working on; that is where maintainers look.
- 4
Open a small pull request
Link the issue in it. A first reply here usually takes 7 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 outsiders282100%
- Got a human reply18265%
- Merged12243%
Time to first reply
After 2 days, 39% of outside PRs had a reply from a person. After a week, 50%. Bots do not count.
The last 52 weeks
Got faster. Median first reply was 42 h over the last four weeks (125 PRs) and 5.7 days over the four before (95 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
- 2
- Stale
- 0
- Has a pull requestSupport profiling without source code changes#20293
- Has a pull requestimprove pjit pytree error involving Nones (and PytreeLeafs)#13074
Issue replies: first human reply in 41 h (median of 213 issues).
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 21:00 and 00:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 68 |
| 01:00 | 67 |
| 02:00 | 70 |
| 03:00 | 60 |
| 04:00 | 42 |
| 05:00 | 28 |
| 06:00 | 22 |
| 07:00 | 11 |
| 08:00 | 8 |
| 09:00 | 10 |
| 10:00 | 10 |
| 11:00 | 5 |
| 12:00 | 11 |
| 13:00 | 17 |
| 14:00 | 14 |
| 15:00 | 12 |
| 16:00 | 12 |
| 17:00 | 29 |
| 18:00 | 41 |
| 19:00 | 38 |
| 20:00 | 46 |
| 21:00 | 77 |
| 22:00 | 147 |
| 23:00 | 137 |
How to start
- Contributing guidefound
- Code of conductnot found
- Issue templatesfound
- Dev container for one-step setupnot found
- No CLA or sign-off requirement was found.
Where the project talks
No chat or mailing list link was found in the README or contributing guide.
Activity
- Commits, 90 days
- 2,035
- Releases, 12 months
- 14
- Active maintainers
- 31
- Last push
- 10 Oct 2026
Stack
Similar repositories
Same main language (Python), most shared frameworks and topics first, then the faster reply.
Automated Machine Learning on Kubernetes
- First reply
- 7.2 days