Not my experience at all. Rust "editions" fairly clearly address many concerns around this. But I do think that crates.io is a wild west in terms of quality an

Not my experience at all. Rust "editions" fairly clearly address many concerns around this. But I do think that crates.io is a wild west in terms of quality and consistency. Just like npm is. And while crates.io is intimately bound up with cargo, and with Rust dev generally, it doesn't equate with Rust. I personally think there's a good argument to be made for certain kinds of closed, commercial software projects to just avoid it entirely and carefully curate their 3rd party deps and avoid going out to crates.io to get them. I'd personally prefer (for some projects) a model of "vendoring" (checking-in) third party dependencies.