Voting starts in March for the Drupal Association Board election.
Having modules enabled, but not in use, can waste precious resources on your server, add security loopholes, and cause confusion for content editors and developers.
This module attempts to correct that by assessing whether various enabled modules are actually in use. For example, if the core blog module is enabled, does at least one blog post exist? Currently this module simply lists modules enabled, and modules enabled, but not in use. Future revisions of the module will allow modules not in use to be disabled in bulk and include Drush integration.
Modules checked for in use status will be added to this page on an ongoing basis. If you'd like to see a new module added, please submit a feature request (and a patch if possible). For each module added, there must be an agreement as to the minimum criteria needed before a module is considered unused.
You may also want to view the module roadmap.
For many modules, it will not be possible or practical to determine if they are in use or not.
Disabling modules should be done on a development and/or staging site first, then a production site after thorough testing.