OWASP/Nettacker
Automated Penetration Testing Framework - Open-Source Vulnerability Scanner - Vulnerability Management
In plain words
Outside PRs: 3 in 10 merged. First reply usually within 3 weeks. Replies slowed down this month.
Outside PRs merged
33%
18 merged, 36 closed, 13 still open
Higher than 6% of 565 other measured repositories
First human reply
3 weeks
median of 67 outside PRs, 33 unanswered
Time to merge
Not enough data
18 of 67 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 slack, 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 3 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 outsiders67100%
- Got a human reply3451%
- Merged1827%
Time to first reply
After 2 days, 37% of outside PRs had a reply from a person. After a week, 46%. Bots do not count.
The last 52 weeks
Slowed down. Median first reply was Not enough data over the last four weeks (14 PRs) and 22 h over the four before (31 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
- 1
- Stale
- 0
- Has a pull requestTranslations needed for comparison functionality messages#905
Issue replies: first human reply in Not enough data (median of 50 issues).
How to start
- Contributing guidefound
- Code of conductfound
- Issue templatesnot found
- 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
- 1
- Active maintainers
- 2
- Last push
- 9 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/OWASP/Nettacker)[](https://contributable.vercel.app/repo/OWASP/Nettacker)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/OWASP/NettackerFor developers: every figure on this page as JSON at /api/v1/repos/OWASP/Nettacker.
Similar repositories
Same main language (Python), most shared frameworks and topics first, then the faster reply.
Index service server
- First reply
- 27 h
- 12 outside PRs
