cargo-supply-chain
Gather author, contributor and publisher data on crates in your dependency graph. (by rust-secure-code)
bpaf
Command line parser with applicative interface (by pacak)
| cargo-supply-chain | bpaf | |
|---|---|---|
| 20 | 21 | |
| 311 | 315 | |
| 1.3% | - | |
| 4.9 | 9.1 | |
| about 1 month ago | 7 days ago | |
| Rust | Rust | |
| 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.
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:
bpaf
Posts with mentions or reviews of bpaf.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-03.
- bpaf – Command line parser with applicative interface
-
Crate to print tables in CLI in a lazy fashion?
If you want to make smart decisions depending on widths of the cells - you have to consume the whole iterator to see what is the widest cell out there, it could be the last one for example. During that iteration you'll want either to store the values somehow or store preformatted bits in a string - something like this https://github.com/pacak/bpaf/blob/master/src/buffer.rs
- The Icculus Microgrant is giving out 250 dollar grants to open source projects, please brag about your project(s) in this thread so I can see them!
-
Announcing clap-markdown — automatically generate Markdown docs for clap command-line tools
bpaf does it here, giving access to primitives like "dump names of this parser" or "dump help for this subparser": https://github.com/pacak/bpaf/blob/semantic/src/docugen.rs
-
Branching based on the return type of a function/closure argument
https://github.com/pacak/bpaf/blob/master/src/from_os_str.rs - a concrete example
- cargo + dynamic shell completion = cauwugo
-
Yet another command line argument parser: bpaf 0.6.0
https://github.com/pacak/bpaf/issues/50 - I would appreciate some feedback from a new user on naming conventions used - there or here is fine.
-
Design comparison of clap and bpaf (arg parsers)
Most of the code change is here: https://github.com/pacak/bpaf/pull/57 https://github.com/pacak/bpaf/pull/60
-
Yet another command line argument parser: bpaf 0.5.5
Something like this, handles example from the ticket at least (sans hex digits) https://github.com/pacak/bpaf/blob/master/examples/sensors.rs
-
Yet another command line argument parser: bpaf 0.5.2
see https://github.com/pacak/bpaf/blob/rc-0.5.5/examples/custom_usage.rs
What are some alternatives?
When comparing cargo-supply-chain and bpaf you can also consider the following projects:
cap-std - Capability-oriented version of the Rust standard library
clap-rs - A full featured, fast Command Line Argument Parser for Rust
paru - Feature packed AUR helper
rustc-dev-guide - A guide to how rustc works and how to contribute to it.
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
argparse-benchmarks-rs - Collected benchmarks for arg parsing crates written in Rust [Moved to: https://github.com/rosetta-rs/argparse-rosetta-rs]
cargo-auditable - Make production Rust binaries auditable
rust-argparse - The command-line argument parser library for rust
eve-rs - A simple, intuitive, express-like HTTP library
argparse-rosetta-rs - Comparing argparse APIs
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
venial - "A very small syn"
cargo-supply-chain vs cap-std
bpaf vs clap-rs
cargo-supply-chain vs paru
bpaf vs rustc-dev-guide
cargo-supply-chain vs cargo-crev
bpaf vs argparse-benchmarks-rs
cargo-supply-chain vs cargo-auditable
bpaf vs rust-argparse
cargo-supply-chain vs eve-rs
bpaf vs argparse-rosetta-rs
cargo-supply-chain vs cargo-msrv
bpaf vs venial