evshary/rust_fuzz_examples — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2026-05-15
Compare eight different Rust testing tools on the exact same intentional bug.
Learn the difference between fuzz testing and property-based testing.
Test multi-threaded Rust code for race conditions using Loom.
Decide which fuzzing tool to adopt based on setup complexity and flexibility.
| evshary/rust_fuzz_examples | abc3dz/mixxx | abyo-software/ferro-stash | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | Rust | Rust | Rust |
| Last pushed | 2026-05-15 | — | — |
| Maintenance | Maintained | — | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 2/5 | 4/5 |
| Audience | developer | general | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires installing Rust nightly or specific fuzzing toolchains depending on which example you run.
A teaching repo with eight side-by-side examples of Rust fuzzing, property testing, and concurrency testing tools, all finding the same intentional bug.
Mainly Rust. The stack also includes Rust, cargo-fuzz, LibAFL.
Maintained — commit in last 6 months (last push 2026-05-15).
License terms are not stated in the explanation.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.