zephyrproject-rtos/zephyr
Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
In plain words
Outside PRs: 6 in 10 merged. First reply usually within 3.6 days. Replies got faster this month.
Outside PRs merged
64%
172 merged, 97 closed, 415 still open
Higher than 20% of 565 other measured repositories
First human reply
3.6 days
median of 684 outside PRs, 92 unanswered
Time to merge
Not enough data
172 of 684 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 mailing list, or on the issue itself. Not in private messages.
Open it - 4
Sign off your commits
Commit with git commit -s. Without the sign-off line the checks fail.
- 5
Open a small pull request
Link the issue in it. A first reply here usually takes 3.6 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 outsiders684100%
- Got a human reply59287%
- Merged17225%
Time to first reply
After 2 days, 43% of outside PRs had a reply from a person. After a week, 59%. Bots do not count.
The last 52 weeks
Got faster. Median first reply was 21 h over the last four weeks (1350 PRs) and 3.7 days over the four before (437 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
- 4
- Has a pull request
- 0
- Stale
- 1
- ClaimedBluetooth: Controller: Use defines for access_addr and crc_init array sizes#40378
- Claimedsyscall stack usage report#27189
- ClaimedAdd documentation for the flash simulator#20654
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 | 130 |
| 01:00 | 99 |
| 02:00 | 57 |
| 03:00 | 41 |
| 04:00 | 36 |
| 05:00 | 25 |
| 06:00 | 19 |
| 07:00 | 20 |
| 08:00 | 29 |
| 09:00 | 37 |
| 10:00 | 38 |
| 11:00 | 74 |
| 12:00 | 168 |
| 13:00 | 239 |
| 14:00 | 241 |
| 15:00 | 217 |
| 16:00 | 217 |
| 17:00 | 238 |
| 18:00 | 240 |
| 19:00 | 234 |
| 20:00 | 237 |
| 21:00 | 215 |
| 22:00 | 177 |
| 23:00 | 150 |
How to start
- Contributing guidefound
- Code of conductfound
- Issue templatesfound
- Dev container for one-step setupnot found
- Commits must be signed off (DCO): use git commit -s.
Where the project talks
Activity
- Commits, 90 days
- 10,498
- Releases, 12 months
- 18
- Active maintainers
- 61
- Last push
- 10 Oct 2026
Stack
Badge and feed
Two ways to use these figures outside this page.
For maintainers: a README badge
Shows newcomers how quickly this project answers and how often it merges. Paste the line into your README; the badge updates with the index.
[](https://contributable.vercel.app/repo/zephyrproject-rtos/zephyr)[](https://contributable.vercel.app/repo/zephyrproject-rtos/zephyr)For contributors: follow new issues
Add the feed to a feed reader (Feedly, Inoreader, Thunderbird) and you hear about new free starter issues here without checking the site.
https://contributable.vercel.app/feed/repo/zephyrproject-rtos/zephyrFor developers: every figure on this page as JSON at /api/v1/repos/zephyrproject-rtos/zephyr.
Similar repositories
Same main language (C), most shared frameworks and topics first, then the faster reply.
No description.
- First reply
- 54 min
