aboutcode-org/scancode-toolkit
:mag: ScanCode detects licenses, copyrights, dependencies by "scanning code" ... to discover and inventory open source and third-party packages used in your code. Sponsored by NLnet, the Google Summer of Code, Azure credits, nexB and other generous sponsors!
In plain words
Outside PRs: 5 in 10 merged. First reply usually within 7 weeks. 1 starter issue is available now. Replies slowed down this month.
Outside PRs merged
45%
5 merged, 6 closed, 37 still open
Higher than 10% of 559 other measured repositories
First human reply
7 weeks
median of 48 outside PRs, 22 unanswered
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
Take this free issue
Report Apache Section 4 notices separately
Open issue #2708 - 3
Know where to ask
Questions go to the project's slack, 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 7 weeks; 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 outsiders48100%
- Got a human reply2654%
- Merged510%
Time to first reply
After 2 days, 13% of outside PRs had a reply from a person. After a week, 27%. Bots do not count.
The last 52 weeks
Slowed down. Median first reply was Not enough data over the last four weeks (24 PRs) and 4 days over the four before (27 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
- 1
- Claimed
- 1
- Has a pull request
- 41
- Stale
- 23
- Has a pull requestSupport `pylock.toml`#4638
- Has a pull requestParse npmrc#4494
- Has a pull requestSupport rust makepkg’s .SRCINFO files#4406
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 16:00 and 19:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 0 |
| 01:00 | 0 |
| 02:00 | 3 |
| 03:00 | 3 |
| 04:00 | 0 |
| 05:00 | 0 |
| 06:00 | 1 |
| 07:00 | 1 |
| 08:00 | 0 |
| 09:00 | 0 |
| 10:00 | 1 |
| 11:00 | 1 |
| 12:00 | 1 |
| 13:00 | 0 |
| 14:00 | 2 |
| 15:00 | 5 |
| 16:00 | 8 |
| 17:00 | 9 |
| 18:00 | 5 |
| 19:00 | 4 |
| 20:00 | 6 |
| 21:00 | 7 |
| 22:00 | 3 |
| 23:00 | 1 |
How to start
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/aboutcode-org/scancode-toolkit)[](https://contributable.vercel.app/repo/aboutcode-org/scancode-toolkit)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/aboutcode-org/scancode-toolkitFor developers: every figure on this page as JSON at .
Similar repositories
Same main language (Python), most shared frameworks and topics first, then the faster reply.
Utility library to parse, normalize and compare License expressions for Python using a boolean logic engine. For expressions using SPDX or
- First reply
