„... another popular solution to fight spam is Antispam Bee“ – Matt Mullenweg, Q&A WordCamp Europe 2014
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 80%
Response Time: 2d
First Timer Success: 100%
pluginkollektiv/antispam-bee has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pluginkollektiv/antispam-bee respond to incoming external pull requests in approximately 51.1 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 62.5 places pluginkollektiv/antispam-bee in the A tier.
The external contributor pull request merge rate for pluginkollektiv/antispam-bee is 79.6%, based on public PR activity from non-core contributors.
pluginkollektiv/antispam-bee currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in pluginkollektiv/antispam-bee. Prompt code reviews with positive guidance for new contributors.
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/pluginkollektiv/antispam-bee?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~33 hours (96% approval). Large PRs (>500 lines) take ~245 hours (36% approval). Keep your diff compact for rapid review.
This is a ticket for collecting thoughts about how 3rd parties could integrate with us. My first thoughts ... I think we need to group our features: Requires mapping to an e-mail or username Trust approved commenters Trust commenters with a Gravatar Requires mapping to a textarea BBCode links are spam Allow comments only in certain language (Privacy!) Requires mapping to various fields (body -> textarea, e-mail, IP ...) Use regular expressions Look in the local spam database No mapping needed Honeypot Consider the comment time Block comments from specific countries New/better spam checks Timecheck via JS to make it compatible with caching Use native Disallowed list from WordPress (Requires mapping to a textarea) Rate limiting by IP Block bad bots / user agents Token (HMAC) Here is an interesting mapping mechanism for CF7: https://contactform7.com/spam-filtering-with-akismet/#deploying-akismet-in-a-contact-form
We should revisit our plugin, if we should change, add or remove something with this change in core: https://make.wordpress.org/core/2026/05/22/extending-unicode-support-in-email-addresses-usernames-and-slugs/ https://make.wordpress.org/core/2026/06/10/call-for-testing-unicode-email-addresses/
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 pluginkollektiv/antispam-bee, 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 pluginkollektiv/antispam-bee acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.6% were successfully merged into the primary branch.
pluginkollektiv/antispam-bee has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. 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 62.5 places pluginkollektiv/antispam-bee in the Welcoming tier.
The external pull request merge rate is 79.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pluginkollektiv/antispam-bee 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 pluginkollektiv/antispam-bee 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.