I wish Rust made it easier to know who the author of a package is (i.e. namespace packages so it's clear in the Cargo.toml), but I do think they've done a better job at designing crates.io than some other package repositories (i.e. npm).
[1] https://boats.gitlab.io/blog/post/2017-10-28-alternative-reg...
[2] https://www.reddit.com/r/rust/comments/9gl8p3/host_local_rep...
In this specific case, most dependencies are authored by people well-known and trusted in the community. The Rust standard library is pretty well-rounded (not compared to Python sense, but it's not like JavaScript either), so they're not something like left-pad or is-odd.
You have there an error handling crate by the second most prolific Rust compiler contributor (if the counts are correct), an OAuth client, an HTTP one, a interactive line editor (like readline), _the_ serialization library in the ecosystem with its JSON support crate, a TOML config parser, the URL parser used by Servo and a crate for determining user paths on Unix.
For instance, you can target a repository and even a specific commit like this in gour cargo.toml file:
[dependencies]
package = { git = "https://github.com/...../something.git", rev = "commit_hash_like_9876541_for_instance" }Don't specify the git repo directly in dependencies unless it's an unpublished crate.
Where are these pulled from? Is this the same game as with other dependency managers in that you blindly trust a tree of code written by random people?