auto-fuzz-test
Effortlessly fuzz libraries with large API surfaces (by rust-fuzz)
pico-args
An ultra simple CLI arguments parser. (by RazrFalcon)
Our great sponsors
| auto-fuzz-test | pico-args | |
|---|---|---|
| 6 | 11 | |
| 69 | 548 | |
| - | - | |
| 0.0 | 3.0 | |
| over 2 years ago | 6 months ago | |
| Rust | Rust | |
| Apache License 2.0 | MIT License |
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.
auto-fuzz-test
Posts with mentions or reviews of auto-fuzz-test.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-15.
-
We Don't Need a Stable ABI
Can confirm, https://github.com/rust-fuzz/auto-fuzz-test was hard write to write (and still isn't production ready) precisely because the compiler doesn't expose type information.
-
Win32 API fuzzer, to help develop Wine
This is super interesting! I've tried auto-generating fuzzing harnesses for arbitrary Rust functions as well: https://github.com/rust-fuzz/auto-fuzz-test
-
The `arbitrary` crate is approaching 1.0!
We've been leaning on this crate heavily in https://github.com/rust-fuzz/auto-fuzz-test, and it's really nice to see support for borrowed types materialize!
-
New:`cargo-fuzzcheck` 0.5.0 and a series of decent, fast-to-compile crates to replace `syn`, `quote`, `serde-json`, and `toml-rs`
Interesting! We'll need to try it with https://github.com/rust-fuzz/auto-fuzz-test, since we're getting mysterious segfaults from our cargo-fuzz/libfuzzer backend right now.
-
Unsafe Rust: How and when (not) to use it - LogRocket Blog
Specifically, I tried leading a fuzzing effort via https://github.com/rust-fuzz/auto-fuzz-test, but right now it's not quite production-ready. We have good progress in proc_macro branch, but that's geared towards crates, and it's not entirely clear how to apply that to the standard library.
-
Does any interesting projects need help?
https://github.com/rust-fuzz/auto-fuzz-test if you want something a bit more involved but with a huge potential
pico-args
Posts with mentions or reviews of pico-args.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-13.
- Improving build times for derive macros by 3x or more
-
Need a new args parser
That's because the maintainer does not consider it an issue but an implementation detail: https://github.com/RazrFalcon/pico-args/issues/15
-
An alternative to clap but with a stable API?
Maybe pico-args then?
-
Immediately off the top of your head what is the best Rust CLI library.
If I forget to get around to it, would you mind poking RazrFalcon/pico-args about adding it to the comparison chart? I really like using that thing as something I can link people to with just a quick explanation of that particular trade-off.
-
Best CLI arg parser for use in Rust to port from Perl with Getopt::Long?
If fewer dependencies is better, you can't get much fewer than pico-args, which has zero dependencies.
- What is the current proper way to get command line args ?
-
Creating an Argparse library [feedback would be appreciated]
You might also want to check out pico-args, Gumdrop, and lexopt to see if any of them meet your needs.
-
Can we please stop downvoting people who dislike Rust?
For example, The Rust compiler isn't slow; we are. and pico-args: Alternatives.
- pico-args: An ultra simple CLI arguments parser with 0 dependencies
-
New:`cargo-fuzzcheck` 0.5.0 and a series of decent, fast-to-compile crates to replace `syn`, `quote`, `serde-json`, and `toml-rs`
For example, I'd love to go from StructOpt to Gumdrop for parsing command-line arguments and cut my compile times and output size by an order of magnitude, but Gumdrop uses String internally, which means it'll panic if it encounters a Windows path with un-paired surrogates or a mojibake'd posix path... some of which I actually have.
What are some alternatives?
When comparing auto-fuzz-test and pico-args you can also consider the following projects:
cargo-auditable - Make production Rust binaries auditable
lexopt - Minimalist pedantic command line parser
rust - Empowering everyone to build reliable and efficient software.
xflags
Win32Fuzzer - Winapi fuzzer to help Wine project in creating better Windows "emulator"
command-line-rust - Code for Command-Line Rust (O'Reilly, 2022, ISBN 9781098109417) https://learning.oreilly.com/library/view/command-line-rust/9781098109424/
json - Strongly typed JSON library for Rust
thiserror - derive(Error) for struct and enum error types
eve-rs - A simple, intuitive, express-like HTTP library
cli-guidelines - A guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.
Qarminer - Qarminer is fuzzer which automatically test Godot and its modules
argh - Rust derive-based argument parsing optimized for code size
auto-fuzz-test vs cargo-auditable
pico-args vs lexopt
auto-fuzz-test vs rust
pico-args vs xflags
auto-fuzz-test vs Win32Fuzzer
pico-args vs command-line-rust
auto-fuzz-test vs json
pico-args vs thiserror
auto-fuzz-test vs eve-rs
pico-args vs cli-guidelines
auto-fuzz-test vs Qarminer
pico-args vs argh