owasp-modsecurity / owasp-modsecurity/ModSecurity-nginx
No new version of the nginx connector has been cut in a long time(2 years)
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 1.9k
- Forks
- 312
- PR merge metrics
- No merged PRs in 30d
Description
Since https://github.com/owasp-modsecurity/ModSecurity-nginx/tree/v1.0.3 there has not been another version cut in a long time of this connector from 2 years ago. Yet master jumps to 233 commits vs v1.0.3 has 209 commits so 20+ commits later. @airween long time no see buddy, If confident in master branch here being stable for a release again, may be worth cutting off a new v1.0.4 version now with all the latest goodies but also not force users to rely on pulling master(which may get breaking changes or issues in it sometime?)
I am still trying to catch up my mod security build/deploy flows on nginx. I see owasp has now officially taken over all components from Spiderlabs which hopefully gets things fixed up sooner with more community leads and bandwidth on the repo.
-Jeremy
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 by comparing the v1.0.3 tag with master, which the issue identifies as having more than 20 additional commits, and determine whether master is stable for release. Done means a new v1.0.4 nginx connector version is cut so users do not need to depend on master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100