How to Contribute to owasp-noir/noir
A practical guide backed by owasp-noir/noir's real pull-request history - not guesswork.
89%
PR merge rate
no recent data
First review
100%
First-timer success
S Tier
C-Rank
Your game plan
1
Pick a starter issue
owasp-noir/noir currently labels 3 open issues as "good first issue". Start there - maintainers expect newcomers on those.
2
Time your pull request
Median first review lands within no recent data. Open your PR when maintainers are active rather than right before a weekend.
3
Keep it small and focused
Outside PRs to this repo are merged at a 89% rate. Small, well-described PRs that pass CI consistently outperform large ones.
4
Engage with review feedback
2 active maintainers review contributions here. Respond to comments promptly - responsiveness is the strongest predictor of getting merged.
Open good first issues
Add detector unit specs for Bottle, Quart, Robyn, Javalin, Dropwizard, Micronaut and Quarkus
#2852Add detector unit specs for seven Go frameworks (Hertz, Huma, GoFrame, Goyave, go-restful, Connect, PocketBase)
#2851Remove always-true `match.size > 0` guards in `tanstack_router.cr`
#2849Rename `golang_spec.cr` to match the `*_lexer_spec.cr` naming in minilexer/
#2723Looking for more? See best Crystal repos for beginners.