heiglandreas

This plugin adds plugins on activation to a composer.json-file and on deactivation removes them.
That way you can handle your plugins via <a href="https://getcomposer.org" rel="nofollow ugc">composer</a>.
Plugins are added to the composer.json via <a href="https://wpackagist.org" rel="nofollow ugc">wpackagist</a> which makes the wordpress-plugin-directory available via git.
But you can also manually add plugins to the pluginlist and on activation the plugin is checked for a composer.json file and if one exists the name is used to add the plugin to the composer.json-File.

Talk to Composer

Add all your active plugins to a composer.json-File.

Juliette Reinders Folmer

The awesome <a href="https://wordpress.org/plugins/plugin-dependencies/" rel="ugc">WordPress Plugin Dependencies</a> plugin introduces plugin dependency management right into your WordPress admin area.
Unfortunately, the reality is that very few plugins currently contain dependency information and until that changes, the effect of having the WordPress Plugin Dependencies plugin activated is minimal.
This plugin enriches the information about dependencies available to the Plugin Dependencies plugin bridging the gap until plugins catch up and start incorporating the <code>Depends</code> and <code>Provides</code> tags in their file headers properly.
<blockquote>
You’ll need to have version 1.3 or higher of the <a href="https://wordpress.org/plugins/plugin-dependencies/" rel="ugc">WordPress Plugin Dependencies</a> plugin installed for this plugin to have any effect.
</blockquote>
<h4>Disclaimer:</h4>
The dependency list provided by this plugin is – and will always be – incomplete.
Additional information to be added to the list is <a href="https://github.com/jrfnl/wp-known-plugin-dependencies/pulls" rel="nofollow ugc">very welcome</a> and will be gracefully accepted.
Even better: send a pull request or bug report to your favorite add-on plugin requesting them to start using the tags.
<h4>Background</h4>
This plugin was inspired by <a href="https://github.com/x-team/wp-plugin-dependencies/issues/34" rel="nofollow ugc">this discussion</a>.
Rather than having individual developers create their own lists to enrich the available information, this plugin tries to bundle the knowledge of dependencies.
The ultimate goal is for the <code>Depends</code> tag to be widely adopted and this plugin to become obsolete.
Of course, it would also help a lot if the Depends/Provides tags would be officially recognized and mentioned in the <a href="https://wordpress.org/plugins/about/faq/" rel="ugc">Plugin Developers FAQ</a> and if what’s expected to be at the top of the main .php file would be as well documented as the readme.txt file in the <a href="https://wordpress.org/plugins/about/" rel="ugc">Developer Center</a>, but that’s a whole other challenge 😉
Any lobbying you can do for this will of course be encouraged and applauded!
If you like this plugin, please <a href="https://wordpress.org/support/view/plugin-reviews/known-plugin-dependencies" rel="ugc">rate and/or review</a> it. If you have ideas on how to make the plugin even better or if you have found any bugs, please report these in the <a href="https://wordpress.org/support/plugin/known-plugin-dependencies" rel="ugc">Support Forum</a> or in the <a href="https://github.com/jrfnl/wp-known-plugin-dependencies/issues" rel="nofollow ugc">GitHub repository</a>.

Known Plugin Dependencies

Add-on plugin for the WordPress Plugin Dependencies plugin, injecting additional information about known dependencies between plugins.

Talk to Composer vs Known Plugin Dependencies