Is your feature request related to a problem? Please describe.
I'm often curious to know why a dependency is listed. Often something is brought in transitively and I can't figure out why. Particularly when developing a package, my goal is to keep the number of dependencies low to avoid version resolution hell and keep the package lightweight.

Describe the solution you'd like
A tooltip that shows the breadcrumb trail(s) that leads to a dependency. (e.g. "ffi -> intl -> characters"), that shows why a package is brought in.

Describe alternatives you've considered
The dependency graph could be hierarchical, starting with the packages that are explicitly mentioned in dependencies and dev_dependencies; those could include their children (although are there problems with circular references?)

Additional context

Don't know if this is even feasible; just random musings.