bmrng
An async MPSC request-response channel for Tokio (by oguzbilgener)
cargo-dephell
Cargo dephell analyzes the third-party dependencies of a Rust workspace (by mimoo)
| bmrng | cargo-dephell | |
|---|---|---|
| 1 | 2 | |
| 11 | 46 | |
| - | - | |
| 0.0 | 1.8 | |
| over 1 year ago | 12 months ago | |
| Rust | HTML | |
| GNU General Public License v3.0 or later | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bmrng
Posts with mentions or reviews of bmrng.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-09-09.
-
Is the crate dependency becoming a problem?
This was exactly what I did to shave a full minute off CI build times (from 3 minutes to 2 minutes) in one of the projects I depended on. However, rather than just removing default-features, I replaced the futures crate entirely with its significantly lightweight sub-crate futures-core when I realized that the project only ever used futures for the Stream trait.
cargo-dephell
Posts with mentions or reviews of cargo-dephell.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-18.
-
Backdooring Rust crates for fun and profit
That's why I started https://github.com/mimoo/cargo-dephell and https://github.com/diem/whackadep btw, to try to get a sense of the risk in our Rust dependencies. The second one is a web UI that can update periodically and shows you what's up with your dependencies. If there's a new update, it'll tell you if it affected a `build.rs` file (which triggers a warning). I wanted to add more rules, like the ones mentioned in the article, but never had the time to do it.
-
Is the crate dependency becoming a problem?
Check whackadep and cargo-dephell: https://github.com/mimoo/cargo-dephell and https://github.com/diem/whackadep
What are some alternatives?
When comparing bmrng and cargo-dephell you can also consider the following projects:
cargo-udeps - Find unused dependencies in Cargo.toml
futures-batch - An adapter for futures, which chunks up elements and flushes them after a timeout — or when the buffer is full. (Formerly known as tokio-batch.)
glog - Leveled execution logs for Go
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
Coerce-rs - Actor runtime and distributed systems framework for Rust
mold - Mold: A Modern Linker 🦠
whackadep - Managing Rust dependencies via a dashboard