InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now. Learn more →
Top 23 Rust Development tool Projects
- Project mention: Just – a handy way to save and run project-specific commands | news.ycombinator.com | 2025-12-15
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
Clippy
A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
cargo, rustfmt, clippy, rust-analyzer, and Rust’s robust unit testing capabilities together form a powerful ecosystem for managing large-scale projects like Spin.
-
- Project mention: Uv format: Code Formatting Comes to uv (experimentally) | news.ycombinator.com | 2025-08-21
If you want to call ruff directly, this doesn't change anything. It's a purely optional feature.
However, to answer the question generally: people want this for the same reason that most people call `cargo fmt` instead of running rustfmt[1] directly: it's a better developer experience, particularly if you don't already think of code formatting as an XY-type problem ("I want to format my code, and now I have to discover a formatter" versus "I want to format my code, and my tool already has that").
[1]: https://github.com/rust-lang/rustfmt
-
-
-
Stream
Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
- Project mention: Static search trees: 40x faster than binary search | news.ycombinator.com | 2024-12-31
Well, I don't use makefiles to deploy software with Rust. I also have never used lex or yacc, but I bet there are similar tools in the ecosystem, or wrappers for those. That would obviate what I will offer below.
Often a new language in a project would define an application boundary. So those would be different containers or services. I may deploy via container images, or an OS specific installer, etc. If we aren't crossing an application boundary I may use FFI. Sometimes I use https://rust-lang.github.io/rust-bindgen/ to smooth that over for C dependencies. There is also a nice concept called a build.rs file: https://doc.rust-lang.org/cargo/reference/build-script-examp.... There's also tools like: https://github.com/casey/just and https://sagiegurari.github.io/cargo-make/
I rarely use multiple languages with Rust. A lot of interpreted languages have bindings through crates and can go in to a project through Cargo. If it involves JS/TS on desktop, I'm usually using Tauri for that. Guess it depends on the system?
Hopefully that helps. You can also still use a Makefile if you want I just haven't dealt with one in a long time.
-
-
Exposing a C ABI for a Rust library is perfectly viable and a nice way to make cross-language bindings.
cbindgen is the recommended crate to generate a C interface for your Rust library:
https://github.com/mozilla/cbindgen
- Project mention: Verus: Verified Rust for low-level systems code | news.ycombinator.com | 2025-04-20
Which means: if the caller guarantees that the parameter ptr is not null, then result.as_ptr() is the same as the passed ptr
That's a kind of trivial contract but Kani tests for all possible pointers (rather than some cherry picked pointers like the null pointer and something else), without actually brute-forcing them but instead recognizing when many inputs test the same thing (while still catching a bug if the code changes to handle some input differently). And this approach scales for non-trivial properties too, a lot of things in the stdlib have non-trivial invariants.
You can check out other proofs here https://github.com/search?q=repo%3Amodel-checking%2Fverify-r...
It's not that different from writing a regular test, it's just more powerful. And you can even use this #[requires] and #[ensures] syntax to test properties in regular tests if you use the https://crates.io/crates/contracts crate.
Really if you have ever used the https://proptest-rs.github.io/proptest/intro.html or the https://crates.io/crates/quickcheck crate, software verification is like writing a property test, but rather than testing N examples generated at random, it tests all possible examples at once. And it works when the space of possible examples is infinite or prohibitively large, too.
-
In this post, I will tell you how I used property testing with the Proptest library in Rust to ensure the correctness of a bunch of generated serialization/deserialization code for the Apache Kafka protocol.
-
-
-
-
- Project mention: Stop struggling with Rust CLI tool installs: the only guide you need (Mac, Linux, Windows) | dev.to | 2025-06-19
cargo-update crate Keep all your installed Cargo tools up-to-date
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Rust Development tools discussion
Rust Development tools related posts
-
Just – a handy way to save and run project-specific commands
-
Blender Addon Development Needs More DevOps
-
Rust Bindings for the Python Interpreter
-
Show HN: Run – a CLI universal code runner I built while learning Rust
-
Good practices for Just: no '../' in pathes.
-
Expert LSP the official language server implementation for Elixir
-
My other email client is a daemon
- A note from our sponsor - InfluxDB www.influxdata.com | 23 Dec 2025
Index
What are some of the best open-source Development tool projects in Rust? This list will help you:
| # | Project | Stars |
|---|---|---|
| 1 | just | 29,314 |
| 2 | PyO3 | 15,007 |
| 3 | Clippy | 12,742 |
| 4 | Rustup | 6,708 |
| 5 | rustfmt | 6,683 |
| 6 | Racer | 3,362 |
| 7 | CodeLLDB | 3,083 |
| 8 | cargo-make | 2,872 |
| 9 | tarpaulin | 2,860 |
| 10 | cbindgen | 2,781 |
| 11 | quickcheck | 2,662 |
| 12 | proptest | 1,991 |
| 13 | rust-cpython | 1,832 |
| 14 | afl.rs | 1,794 |
| 15 | cargo-release | 1,503 |
| 16 | jni-rs | 1,490 |
| 17 | cargo-update | 1,428 |
| 18 | cargo-modules | 1,183 |
| 19 | xargo | 1,125 |
| 20 | clog-cli | 899 |
| 21 | Mockito | 764 |
| 22 | j4rs | 718 |
| 23 | stainless | 458 |