This idea started as a suggestion for a contrib module, but it seems it'll only work if it's a core feature...
The above linked issue has more details, but the summary is that we could create a new hook that modules implement in order to determine whether they're in use or not. This would then allow a report of modules that are enabled on a site, but aren't being used (and so can be safely uninstalled, or configured so they're actually used).
For example, the core Contact module would implement this hook and return TRUE if there are no contact categories. The Taxonomy module would return TRUE when there are no vocabularies. The Link module would return TRUE when there are no Link fields.
The hard part will be getting contrib modules to implement this hook, but if/once they do, I think this'll be a really handy feature to help clean up sites.
Recent comments
I’ve been looking into different ways to handle integrations more efficiently, and the approach you mentioned here clarifies a few things I was stuck on. Definitely going to try implementing...
Integration
It’s really interesting that clearing out the menu_links table and reinstalling the Admin Bar module did the trick. Menu corruption is such a common headache when moving from D7 to Backdrop,...
Upgrading from Drupal 7 - problem
Restore Newsletter Subscriptions from a Dev Website In my last comment, I described a way to restore newsletter subscriptions from a database backup. The method involved directly editing...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled