A plugin for Flake8 finding likely bugs and design problems in your program. Contains warnings that don't belong in pyflakes and pycodestyle.
C-Rank Grade: B (Solid) - 63/100
External PR Merge Rate: 78%
Response Time: 16h
First Timer Success: 67%
PyCQA/flake8-bugbear has a recorded first-timer success rate of 66.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PyCQA/flake8-bugbear respond to incoming external pull requests in approximately 16.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 63.4 places PyCQA/flake8-bugbear in the B tier.
The external contributor pull request merge rate for PyCQA/flake8-bugbear is 77.8%, based on public PR activity from non-core contributors.
PyCQA/flake8-bugbear currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in PyCQA/flake8-bugbear 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/PyCQA/flake8-bugbear?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (96% approval). Large PRs (>500 lines) take ~77 hours (35% approval). Keep your diff compact for rapid review.
In an older code blob of mine I came across this oddity: for a, b, _ in zip(iter_a, iter_b, iter_c): ... which should be simplified to for a, b in zip(iter_a, iter_b): ... by removing iter_c entirely. Turns out I had this pattern in two other places as well 🤦🏻♂️ Would this not be a useful idiom to look for and warn about? (Assuming _ isn’t used in the body of the loop…)
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 PyCQA/flake8-bugbear, 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 PyCQA/flake8-bugbear acknowledge new external contributions in approximately 15 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.8% were successfully merged into the primary branch.
PyCQA/flake8-bugbear has a recorded first-timer success rate of 66.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~15 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 63.4 places PyCQA/flake8-bugbear in the Solid tier.
The external pull request merge rate is 77.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, PyCQA/flake8-bugbear currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for PyCQA/flake8-bugbear 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.