Backups & maintenance · Explainer
What Happens When a Plugin Is Closed on WordPress.org
Short answer
When WordPress.org closes a plugin, the plugin page shows a closure notice, new downloads stop, and no new updates reach your site. A copy already installed on your site keeps running until you remove it, so you must check the reason and replace it if the closure was for a security issue.
Key takeaways
- A closed plugin can no longer be downloaded from WordPress.org or installed from the WordPress admin.
- An installed copy keeps running after closure, so closure alone does not remove it from your site.
- WordPress.org shows the closure reason only after 60 days, in broad terms such as Security Issue.
- A plugin closed for a security issue can reopen after the developer fixes the issue and replies to the Plugins Team.
- A plugin closed at the author's request is meant to stay closed, so plan for a replacement.
- Check every installed plugin on its WordPress.org page, because WordPress does not alert you in the admin.
What does “closed” mean on WordPress.org?
A closed plugin is a plugin that WordPress.org has removed from public download in its directory.
The Plugin Developer FAQ says that when a plugin is closed, the page shows as closed and the zip files are no longer generated. That fact was last updated on 10 November 2026.
Closure is a directory action, not a change to your server. It stops new people from getting the plugin, but it does not delete files from sites that already have it.
Why does WordPress.org close a plugin?
WordPress.org closes a plugin for a security issue, a guideline violation, a licensing problem, an author request, or a merge into WordPress itself.
The Detailed Plugin Guidelines say that a plugin found to have security issues will be closed until the situation is resolved. The same guidelines say violations may result in plugins being removed from the directory until the issues are resolved.
The Directory Maintenance handbook lists cases where plugins are closed at once. Those cases are security issues, GPL violations, flagrant abuse of other community members, a banned user, and disguising a plugin to get around a past block or ban.
Email can also lead to closure. The Make WordPress Plugins team has said that a plugin can be closed when the owner email bounces and the team has no way to reach the developer.
What happens to a plugin you already installed?
A plugin already installed on your site keeps running after WordPress.org closes it.
Closure does not deactivate the plugin, delete its files, or remove its settings. Your site keeps using the same code that was live before the closure date.
That is why a security closure needs fast action. If the code had a flaw, that flaw stays on your site until you remove the plugin or replace it with a fixed version.
A closure for another reason is less urgent, but it still ends support from the directory. You will get no bug fixes, no new features, and no compatibility updates for new WordPress releases.
What happens to new installs and updates?
New installs stop, and updates stop, as soon as WordPress.org closes a plugin.
The Plugin Developer FAQ says no one can download the plugin from the website, and no one can install it from the WordPress admin. The update system has no new public release to offer your site.
Your admin screen may still look normal. WordPress does not add a warning on the Plugins screen for a closed plugin, so a closed plugin can sit there for months with no update offered.
The code stays open in one place. The FAQ says the SVN repository will remain accessible, so others can download and fork the code if they wish.
What does the closed plugin page show, and when?
A closed plugin page shows a closure notice with a date, and it shows the broad reason after 60 days.
The Alerts and Warnings handbook says that, as of November 2017, closed plugins display a notice that all visitors can see. Plugins closed after January 2018 also include a date.
After 60 days, the alert is updated to explain why the plugin was closed. The reason is shown only in broad terms, and no explicit details are given.
The handbook lists 5 reasons, shown in the table below.
| Reason | What it means |
|---|---|
| Security Issue | A security concern has been found in the plugin |
| Author Request | The author has asked for the plugin to be closed |
| Guideline Violation | The plugin broke a directory guideline |
| Licensing/Trademark Violation | Non-GPL code is in use, or a trademark is misused |
| Merged Into Core | The feature is now part of WordPress itself |
More detail goes only to the WordPress.org security team and the plugin authors, unless there is an extreme circumstance. That limit is stated in the same Alerts and Warnings handbook.
Can a closed plugin come back?
Some closed plugins can reopen, but a plugin closed at the author's request is meant to stay closed.
The Plugin Developer FAQ says that a plugin closed for a security reason can reopen in most cases. The developer must fix the issue and reply to the email from the Plugins Team.
A guideline closure depends on the severity and nature of the violation. Repeat offenders are less likely to have a plugin reopened than first-time offenders.
A developer can also close a plugin on purpose. As of April 2020, a developer can close their own plugin at any time from the advanced tab on the plugin page, in the “CLOSE THIS PLUGIN” section.
If a plugin has more than 10,000 users, the developer must email the Plugins Team and request closure. The FAQ says closing a plugin by request is intended to be permanent.
How do you check if a plugin on your site is closed?
Open each installed plugin on WordPress.org and look for a closure notice on its page.
Start in your admin at “Plugins → Installed Plugins” and note each plugin name. Then open its page in the WordPress.org plugin directory and read the top of the page.
A closed page states the closure date and that the plugin is not available for download. If the closure is less than 60 days old, the page may show no reason yet.
Also check the last update date and the tested-up-to version on the same page. Plugins that do not support the last 3 major releases of WordPress get a separate warning, as stated in the Alerts and Warnings handbook.
A security plugin can help you spot a removed plugin, but it is not a full check. Manual checks of the directory pages remain the direct source.
What should you do after a plugin is closed?
Treat a security closure as urgent, back up your site, then replace the plugin.
First, read the reason on the plugin page if 60 days have passed. If the reason is Security Issue, or if the closure is too new to show a reason, act as if the code may be unsafe.
Next, make a backup before you change anything. Follow the steps in how to back up WordPress so you can restore the site if the replacement breaks a feature.
Then find a replacement that is still listed, updated, and tested with recent WordPress releases. Check its last update date, its active install count, and its support page before you install it.
After you install the replacement, test the feature it covers. Check forms, menus, shortcodes, and any pages that used the old plugin, then deactivate and delete the closed plugin.
If the closed plugin held data you need, export that data before you delete it. Some plugins store settings and content in the database, and deletion can remove that data.
A backup tool can make the restore step simpler. See the backup plugins page for options that fit this kind of change.
What myths about closed plugins should you ignore?
The most common myth is that closure deletes the plugin from your site, and it does not.
Another myth is that a closed plugin is always unsafe. Some closures are for an author request, a merge into WordPress, or a licensing issue, and those reasons do not prove the code had a security flaw.
A third myth is that you can wait for an update. A closed plugin gets no updates from WordPress.org, so waiting leaves the same code in place.
A fourth myth is that a new version will appear under the same name. A closed plugin can be taken over by a new developer, but that takes a formal process and a full review, as described in the Take Over an Existing Plugin handbook.
What mistakes should you avoid?
Do not keep a closed security plugin running while you look for a replacement.
Do not download a copy of the closed plugin from an unknown site. The directory no longer offers it, and a copy from another source may be changed or out of date.
Do not delete the plugin before you back up and export its data. A backup lets you restore the site, and an export lets you keep content tied to the old plugin.
Do not assume a replacement is safe because it is popular. Check its update date, its tested-up-to version, and its reviews, then test it on your site.
For a security closure, a dedicated security tool can add a check after you replace the plugin. The Wordfence review describes one tool that scans for known plugin problems.
Use a backup tool before you remove a plugin. The UpdraftPlus review describes one option for that step.
Frequently asked questions
Is it safe to keep a plugin that was closed on WordPress.org?
It depends on the reason. A closure for a security issue means you should replace the plugin at once, because the flaw stays in the installed code. A closure for an author request or a merge into WordPress is less urgent, but you still get no updates, so you should plan a replacement and check the feature it provided.
Will WordPress tell me if a plugin on my site is closed?
No. WordPress does not show a closure warning on the Plugins screen, and a closed plugin simply stops receiving updates. You must check each plugin on its WordPress.org page, where a closure notice, a date, and after 60 days a broad reason will appear.
Can I still download a closed plugin from WordPress.org?
No. When a plugin is closed, WordPress.org stops generating its zip files, so no one can download it from the website or install it from the WordPress admin. The source code may still be reached in the SVN repository, but that is not a normal install route for most site owners.
How long does it take for WordPress.org to show why a plugin was closed?
The reason appears after 60 days. Before that, the page shows the closure notice and the closure date, but not the reason. After 60 days, the page shows one of five broad reasons: Security Issue, Author Request, Guideline Violation, Licensing or Trademark Violation, or Merged Into Core.
Can someone else take over a closed plugin?
Sometimes, but it is a formal process. The person who wants to take over must try to contact the original developer, and if there is no reply after 30 days they can send their fixed code to the Plugins Team. The code then goes through a normal review, and a plugin closed for a security issue must have all those issues fixed first.
What should I do first if a plugin I use is closed for a security issue?
Back up your site, then replace the plugin. Do not keep the closed plugin active while you search, and do not download a copy from an unknown site. Install a maintained replacement, test the feature it covers, then deactivate and delete the closed plugin.
Sources
- Plugin Developer FAQ WordPress Developer Resources
- Alerts and Warnings WordPress Developer Resources
- Detailed Plugin Guidelines WordPress Developer Resources
- Directory Maintenance Make WordPress Plugins
- Take Over an Existing Plugin WordPress Developer Resources
- Retired Official Core Team Plugins Make WordPress Core
- Plugin Developer FAQ (handbook mirror) GitHub
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
