Track module dependencies

Problem/Motivation

I am auditing a site's module's and would like a way to quickly tell if a module was installed as a dependency.

We currently have the ability to create views that shows modules and notes, but without this, it's lacking relevant info from the modules page.

The modules page lists all modules requiring and required by each module, with enabled modules highlighted.

This data currently comes from a theme hook in system.admin.inc, which populates a details element.

Can that be used as a views field and/or to record with module updates?

I'm thinking that if a module was installed as a dependency, but the dependent module was uninstalled or the dependency dropped, we'd be able to add a view filter to find modules without dependencies, or use the module history and highlight dependency changes.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes