The Future of Rust

By doing so, not only one can see how many unsafe code, tests and documentation there are in the library, but one can also see if the crate is too complex for its own good: if you do not feel comfortable to contribute or maintain a crate you’re evaluating, it might not be a good idea to use it. Since it’s so easy to add a new crate to our project, we tend to include too much dependencies in our own project. We won’t write in our reviews things like:

Because our resources are limited and because other people can easily write such reviews, we’ll mostly focus of what we consider the most important:

The last point might seem weird, but some very popular crates do not provide much features and since we want to reduce the number of dependencies in our ecosystem, it makes sense to flag these crates in order to reduce their usage.

Source: antoyo.ml