Currently, crates.io and crates.rs list only direct dependencies of each crate, but not the full list of dependencies-of-dependencies, so you don't actually see everything that a crate pulls in.
I'd like to improve it by also showing a few "notable" dependencies-of-dependencies. The full tree would be too big and too noisy to be helpful at the first glance, so I'd like to filter it down to only interesting subdependencies out of that tree and show them alongside direct dependencies.
Which dependencies should be shown?
I'm assuming that there are some dependencies that you may want to be warned about, e.g. maybe they're too heavy, not supported on your platform, or require 3rd party tools or libraries that you don't have installed.
For example, I'd highlight when a crate ends up unconditionally depending on bindgen
(likely via some -sys crate), because that's a fairly heavy compile-time dependency and I don't always want to install llvm. It's not meant to say a dependency is "bad", but help make a decision whether crate's dependencies are suitable and avoid surprises.
Are there crates you'd like to nominate?