Download the PHP package typisttech/wp-org-closed-plugin without Composer
On this page you can find all versions of the php package typisttech/wp-org-closed-plugin. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download typisttech/wp-org-closed-plugin
More information about typisttech/wp-org-closed-plugin
Files in typisttech/wp-org-closed-plugin
Package wp-org-closed-plugin
Short Description Composer plugin to mark packages as abandoned if closed on WordPress.org
License MIT
Homepage https://github.com/typisttech/wp-org-closed-plugin
Informations about the package wp-org-closed-plugin
Composer plugin to mark packages as abandoned if closed on WordPress.org
Built with ♥ by Typist Tech
Usage
Once installed, use composer as usual.
[!TIP] Hire Tang Rufus!
I am looking for my next role, freelance or full-time. If you find this tool useful, I can build you more weird stuff like this. Let's talk if you are hiring PHP / Ruby / Go developers.
Contact me at https://typist.tech/contact/
Why
When a plugin is closed on WordPress.org, WPackagist not always remove it from its database immediately. As a result, some closed plugins remain available for installation via WPackagist.
Moreover, even if a plugin is closed, its existing versions are still downloadable from WordPress.org and the subversion repository.
To catch these closed plugins, WP Org Closed Plugin queries WordPress.org API to check whether a plugin is closed and mark them as abandoned in Composer.
What to do when a plugin is closed?
It depends on why the plugin is closed.
For security concerns, stop using the plugin immediately.
For plugin exodus, install the plugin via the new repository suggested by the plugin author.
For other reasons, do your own research.
Caveats
No longer maintained
Composer hardcodes the message no longer maintained
for abandoned packages.
Plugins closed on WordPress.org may be closed for various reasons - some are permanent, some are temporary.
The message no longer maintained
may not be accurate in some cases.
You should check the plugin's WordPress.org page for more details.
No replacement was suggested
There is no way to suggest a replacement when closing a plugin on WordPress.org.
You should do your own research to find suitable replacements.
Locked File
Since plugin closure might be temporary, WP Org Closed Plugin does not modify composer.lock.
Thus, $ composer audit --locked will not report closed plugins.
You should run composer audit without --locked to check for closed plugins.
Cache
WordPress.org API responses are cached for 10 minutes.
If you must clear the cache, delete the <composer-cache-dir>/wp-org-closed-plugin directory.
Why allow_self_signed when connecting to https://api.wordpress.org?
[!IMPORTANT] Help Wanted!
Please send pull requests if you know how to get around the error:
It is a hack to disallow HTTP/3, forcing HttpDownloader to use RemoteFilesystem instead of CurlDownloader.
I suspect api.wordpress.org does not properly support HTTP/3:
See:
- https://github.com/composer/composer/pull/12363
- https://github.com/composer/composer/blob/f5854b140ca27164d352ce30deece798acf3e36b/src/Composer/Util/HttpDownloader.php#L537
- https://github.com/typisttech/wp-org-closed-plugin/pull/22
[!TIP] Hire Tang Rufus!
There is no need to understand any of these quirks. Let me handle them for you. I am seeking my next job, freelance or full-time.
If you are hiring PHP / Ruby / Go developers, contact me at https://typist.tech/contact/
Installation
Credits
WP Org Closed Plugin is a Typist Tech project and maintained by Tang Rufus, freelance developer for hire.
Full list of contributors can be found on GitHub.
Copyright and License
This project is a free software distributed under the terms of the MIT license. For the full license, see LICENSE.
Contribute
Feedbacks / bug reports / pull requests are welcome.
All versions of wp-org-closed-plugin with dependencies
composer-plugin-api Version ^2.6