owasp-modsecurity / owasp-modsecurity/ModSecurity
Review all repositories under owasp-modsecurity org and retire the ones no longer needed
Open
Nobody has claimed this yet.
admin (OWASP transfer)
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
Trustwave Spiderlabs has the following repos with a connection to ModSecurity. 4 of them have been transferred as of this writing (2024-01-28):
- https://github.com/SpiderLabs/ModSecurity (has been transferred)
- https://github.com/SpiderLabs/ModSecurity-nginx (has been transferred)
- https://github.com/SpiderLabs/ModSecurity-apache (has been transferred)
- https://github.com/SpiderLabs/modsec-sdbm-util
- https://github.com/SpiderLabs/ModSecurity-Python-bindings
- https://github.com/SpiderLabs/ModSecurity-log-utilities
- https://github.com/SpiderLabs/secrules-language-tests (has been transferred)
- https://github.com/SpiderLabs/modsecurity-mlogc-ng
- https://github.com/SpiderLabs/secrules-language-evaluation
- https://github.com/SpiderLabs/ModSecurity-pcap
- https://github.com/SpiderLabs/ModSecurity-status
So there are 3 tasks ahead:
- Get all the remaining repos
- Evaluate all repos and document them
- Retire the ones we no longer need
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the remaining SpiderLabs repositories listed in the issue and inventory which have been transferred. Evaluate each repository and document its status and purpose, then identify the ones no longer needed for retirement. Done means all remaining repositories are obtained, evaluated, documented, and have a recorded retirement decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100