Daemon to ban hosts that cause multiple authentication errors
C-Rank Grade: B (Solid) - 50/100
External PR Merge Rate: 53%
Response Time: 6h
First Timer Success: 50%
fail2ban/fail2ban has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in fail2ban/fail2ban respond to incoming external pull requests in approximately 6.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 50.1 places fail2ban/fail2ban in the B tier.
The external contributor pull request merge rate for fail2ban/fail2ban is 53.3%, based on public PR activity from non-core contributors.
fail2ban/fail2ban does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Active maintainer team in fail2ban/fail2ban welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/fail2ban/fail2ban?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (67% approval). Large PRs (>500 lines) take ~29 hours (24% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
No cached good first issues currently tracked for fail2ban/fail2ban.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to fail2ban/fail2ban, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of fail2ban/fail2ban acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 53.3% were successfully merged into the primary branch.
fail2ban/fail2ban has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 50.1 places fail2ban/fail2ban in the Solid tier.
The external pull request merge rate is 53.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
fail2ban/fail2ban does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for fail2ban/fail2ban are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.