Is Antispam Bee still maintained?
Yes. The WordPress.org directory shows the last release of Antispam Bee on 23 August 2026, tested up to WordPress 7.1.3. On the evidence the directory publishes, there is nothing here that should worry you.
The evidence
Every figure below is read from the WordPress.org plugin directory. Nothing here is our assessment of the code.
| Last release | 23 August 2026 (one month ago) |
|---|---|
| Current version | 2.11.13 |
| Tested up to | WordPress 7.1.3 (current is 7.1.3) |
| Requires PHP | 5.2 |
| Active installs | At least 700,000 sites (the directory reports a rounded floor, not an exact count) |
| Support threads | 1 in the last two months, too few for the share resolved to mean much |
| Directory status | Listed |
| Read from the directory | 21 October 2026 |
What these signals mean
Two things the directory publishes say a plugin is being kept up, and this one shows both: a recent release, and a tested-up-to version close to current WordPress. Neither is about the quality of the code. They are about whether anyone will be there when something changes underneath it.
That is worth checking again in a year rather than treating as settled. Plugins change hands, authors move on, and a plugin that is maintained today is not automatically maintained at the next WordPress release.
What to do about it
Nothing. Keep it updated and check again in a year.
If you are choosing between this and something else, the maintenance signals here are the ones worth weighing: they say more about whether the plugin will still work after the next WordPress release than a feature comparison does.
Is a site you look after running Antispam Bee?
Our free WordPress plugin checker reads any public site and lists the plugins it loads, with the same maintenance signals as the table above for each one. No login and no signup, so it works on a client’s site before you have access to it.
How Antispam Bee compares in its category
The WordPress.org directory files Antispam Bee under the "anti-spam" tag. We read the first 24 plugins the directory lists there and kept the ones that have shipped a release in the last year and are installed on at least 10,000 sites. Each author picks their own plugin's tags, so sharing one means two plugins are listed side by side, not that they do the same job.
| Plugin | Active installs | Last release |
|---|---|---|
| Akismet Anti-spam | At least 5 million sites | 18 August 2026 |
| Antispam Bee (this plugin) | At least 700,000 sites | 23 August 2026 |
| WP Armour | At least 400,000 sites | 3 September 2026 |
| CF7 Apps | At least 300,000 sites | 29 September 2026 |
One plugin in the table is on more sites than Antispam Bee: Akismet Anti-spam leads with at least 5 million sites, against at least 700,000 sites for Antispam Bee. An install count measures how many sites depend on a plugin, not how good it is. What reach does buy is a larger pool of people who notice a breaking change early and report it.
Two of the others have released since Antispam Bee last did on 23 August 2026, most recently CF7 Apps on 29 September 2026. All of them released within 42 days of each other, so on this signal there is nothing between them.
Nothing here is a reason to move off Antispam Bee. Every plugin in the table passes the same maintenance bar this page applies to it, so the comparison is for choosing between them, and what each one actually does on your site should decide that.
Related plugin checks
- Is CookieYes still maintained? Updated 14 October 2026, current against recent WordPress. Nothing of concern.
- Is Complianz still maintained? Updated 13 October 2026, current against recent WordPress. Nothing of concern.
- Is Classic Editor still maintained? Updated 28 May 2026, current against recent WordPress. Nothing of concern.
- Is Advanced Custom Fields still maintained? Updated 10 September 2026, current against recent WordPress. Nothing of concern.
- Is Custom Post Type UI still maintained? Updated 14 July 2026, current against recent WordPress. Nothing of concern.
Related links
- Which WordPress plugins are still maintained? Every plugin we check, with its last release.
- Custom WordPress plugin development When Antispam Bee has to be replaced or taken over and nothing in the directory fits.
Link to this check
Maintain Antispam Bee, or write about it? This badge links to this page, so your readers can see the same evidence. Copy the HTML below.
<a href="https://zignites.com/plugin-check/antispam-bee"><img src="https://zignites.com/badges/plugin-checker.svg" alt="Maintenance signals for Antispam Bee, checked with Zignites Plugin Checker" width="232" height="20"></a>Questions
When was Antispam Bee last updated?
The WordPress.org directory records its most recent release as 23 August 2026. That date is read from the directory each time this page is built, and the page states when it was read.
How can I tell if a WordPress plugin is still maintained?
Three things, all published by the directory on the plugin's own listing: how long ago the last release was, which WordPress version the author says they tested against, and whether the directory still lists it. None of them is about code quality. Together they say whether anybody will be there when PHP or WordPress changes underneath the plugin, which is what actually decides whether it keeps working.
Is Antispam Bee a security risk?
We do not know, and nothing on this page is a security finding. Vulnerability data for WordPress plugins sits behind paid commercial APIs, and guessing at it from a version number either alarms people about plugins that are fine or implies that everything unflagged has been checked and is safe. Both are worse than saying nothing. What this page reports is maintenance: when the plugin last shipped, which WordPress version its author last tested against, and whether the directory still lists it. Those are facts the directory publishes, and they are what predicts whether a plugin will still work after the next core release.
Read from the WordPress.org plugin directory on 21 October 2026. We report maintenance signals only, and never claim a plugin is insecure. All plugins we cover.