xflags
By matklad
cargo-supply-chain
Gather author, contributor and publisher data on crates in your dependency graph. (by rust-secure-code)
xflags | cargo-supply-chain | |
---|---|---|
6 | 20 | |
73 | 311 | |
- | 1.3% | |
5.2 | 4.9 | |
about 1 month ago | about 1 month ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
xflags
Posts with mentions or reviews of xflags.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-11.
-
Started using Rust for scripting
3) xflags is my preferred way to parse CLI arguments for such scripts. It's not good at all, but, for me, it's the best for the task at the moment.
- Announcement: xflags 3.0.0
-
pico-args: An ultra simple CLI arguments parser with 0 dependencies
You might like xflags. It has a similar design philosophy, but is willing to compromise on simplicity a bit to get auto-generated help.
-
Announcement: xflags, fast-to-compile proc macro for cli args
See also https://github.com/matklad/xflags/issues/3
-
Argument parsers that don't choke on invalid unicode
Added https://github.com/matklad/xflags/blob/master/examples/non-utf8.rs.
cargo-supply-chain
Posts with mentions or reviews of cargo-supply-chain.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-04.
-
Release of Structsy 0.5
Great news! Sounds like a good way to add caching to cargo supply-chain. There's a lot of small chunks of data we want to persist.
-
greater supply chain attack risk due to large dependency trees?
Shameless plug: https://github.com/rust-secure-code/cargo-supply-chain shows the supply chain attack surface for your Rust project.
-
Announcement: xflags 3.0.0
bpaf: https://github.com/rust-secure-code/cargo-supply-chain/blob/29bfcb256001cdef46830544b554d33c56602030/src/cli.rs
-
Yet another command line argument parser: bpaf 0.5.2
I'm very happy with it for cargo supply-chain. I appreciate that it has no unsafe code, no sprawling dependency tree, and supports OsStr in addition to just &str.
-
Best way to protect a project from supply chain attacks?
cargo supply-chain to see your attack surface for supply chain attacks
- Cargo-supply-chain: Rust author, contributor and publisher data for dep. crates
-
Comparing Rust supply chain safety tools
See also: cargo supply-chain
-
Yet another command line argument parser: bpaf 0.4.0
I've used bpaf for cargo supply-chain and I'm very happy with it.
-
Fundamental - finding out who you can fund in dependency tree
https://github.com/rust-secure-code/cargo-supply-chain can also help here.
-
Announcing `cargo supply-chain` v0.3: revamped CLI, separate JSON schema
cargo supply-chain list the publishers of all crates in your dependency graph. With it you can: