Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Top 23 Rust cargo-subcommand Projects
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
cargo-public-api
List and diff the public API of Rust library crates between releases and commits. Detect breaking API changes and semver violations via CI or a CLI.
-
cargo-supply-chain
Gather author, contributor and publisher data on crates in your dependency graph.
-
cargo-multivers
Cargo subcommand to build multiple versions of the same binary, each with a different CPU features set, merged into a single portable optimized binary
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
cargo-make aims to be an extensive Rust-written task runner that additionally lets you define workflows to execute your tasks. You can install it using cargo install cargo-make.
cargo-nextest describes itself as a “next-generation Rust test runner”. To install, you need to run cargo install cargo-nextest.
Project mention: Please add licenses to your projects, rust DS emulator Dust now dead. | /r/rust | 2023-06-28Tip: You can check the licenses of all your dependencies (recursively) using cargo-deny: https://github.com/EmbarkStudios/cargo-deny
My problem with maintaining a changelog during development is it can serve as a source of merge conflicts. Instead, I follow Covnentional Commit style and manually write my changelog entries based on the commits. I have a tool [0] that can show me the relevant commits for a package in my repo and automates the entire release process, including doing sanity checks.
I also feel like releasing from CI is hard, especially if you have multiple packages in a repo [1], including
- You can't as easily introspect the process
- You can't as easily recover from failure
- Getting a lot of the nuance right, like handling releases concurrent to merging of PRs, is difficult
- When the workflow is an ever-present "release PR" that you merge when ready has issues with selecting which packages to release and at what version
I have been considering making a tool to generate changelogs from fragments. Been keeping notes at https://github.com/epage/epage.github.io/issues/23
[0]: https://github.com/crate-ci/cargo-release
[1]: https://github.com/MarcoIeni/release-plz/discussions/1019
Project mention: Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux | news.ycombinator.com | 2024-02-17https://github.com/rust-cross/cargo-zigbuild
I’m curious what the blockers are for rustc to cross-compile like zig does natively.
Project mention: Performance difference between obj.function(...) and function(obj, ...) ? | /r/rust | 2023-12-08cargo asm might be useful here (if you can't use godbolt).
Project mention: Performance difference between obj.function(...) and function(obj, ...) ? | /r/rust | 2023-12-08
cargo-machete is a Cargo plugin for cutting out unused dependencies from your project. To install it, you can use cargo install cargo-machete then use cargo machete in a Rust project directory.
Further we use cargo-auditable and cargo-audit as part of both our pipeline and regular scanning of all deployed services. This makes our InfoSec and Legal super happy since it means they can also monitor compliance with licenses and patch/update timings.
Project mention: Distcc: A fast, free distributed C/C++ compiler | news.ycombinator.com | 2023-06-01Hi Rusty!
For a later hack in the same vein, check out https://github.com/sourcefrog/cargo-mutants
Project mention: [Review] Introducing cargo-xwin: A Solution for Cross-Compiling Rust on macOS to MSVC | /r/rust | 2023-05-25Today, I am excited to introduce a real game-changer - the [cargo-xwin](https://github.com/rust-cross/cargo-xwin) crate! After countless trials and errors, cargo-xwin was the only one that truly met my needs.
Project mention: Building cross-platform Rust for Web, Android and iOS – a minimal example | news.ycombinator.com | 2023-07-09I found https://github.com/antoniusnaumann/cargo-swift pretty nice for iOS. It uses UniFFI under the hood but automates the other pieces with building an xcode project.
Rust cargo-subcommand related posts
- Rust Tooling: 8 tools that will increase your productivity
- Performance difference between obj.function(...) and function(obj, ...) ?
- Cargo-zigbuild: Compile Rust using Zig as linker for easier cross compiling
- [Review] Introducing cargo-xwin: A Solution for Cross-Compiling Rust on macOS to MSVC
- Compiling Linux to Mac in CI/CD
- Is there a simple way to borrow the value of an Option without using a match statement?
- Customizable testing framework
-
A note from our sponsor - InfluxDB
www.influxdata.com | 25 Apr 2024
Index
What are some of the best open-source cargo-subcommand projects in Rust? This list will help you:
Project | Stars | |
---|---|---|
1 | cargo-make | 2,392 |
2 | nextest | 1,943 |
3 | cargo-deny | 1,542 |
4 | cargo-release | 1,244 |
5 | cargo-zigbuild | 1,198 |
6 | cargo-asm | 1,104 |
7 | cargo-show-asm | 581 |
8 | cargo-machete | 546 |
9 | cargo-auditable | 547 |
10 | cargo-mutants | 437 |
11 | cargo-c | 414 |
12 | cargo-public-api | 342 |
13 | cargo-readme | 337 |
14 | cargo-supply-chain | 311 |
15 | cargo-wix | 288 |
16 | cargo-xwin | 280 |
17 | cargo-n64 | 151 |
18 | cargo-multivers | 146 |
19 | cargo-deadlinks | 143 |
20 | cargo-swift | 114 |
21 | cargo-aur | 74 |
22 | cargo-changelog | 23 |
23 | cargo-select | 16 |
Sponsored