cargo fuzz

Other Community

Skill notes

When to Use

cargo-fuzz is currently the primary and most mature fuzzing solution for Rust projects using Cargo. Fuzzer · Best For · Complexity cargo-fuzz · Cargo-based Rust projects, quick setup · Low AFL++ · Multi-core fuzzing, non-Cargo projects · Medium LibAFL · Custom fuzzers, research, advanced use cases · High

Quick Start

Initialize and run:

Installation

cargo-fuzz requires the nightly Rust toolchain because it uses features only available in nightly.

Prerequisites

Rust and Cargo installed via rustup Nightly toolchain

Project Structure

cargo-fuzz works best when your code is structured as a library crate. If you have a binary project, split your main.rs into: Initialize fuzzing: This creates:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview cargo-fuzz.preview
# Interpreting Output

| Output | Meaning | |--------|---------| | `NEW` | New coverage-increasing input discovered | | `pulse` | Periodic status update | | `INITED` | Fuzzer initialized successfully | | Crash with stack trace | Bug found, saved to `fuzz/artifacts/` | Corpus location: `fuzz/corpus/fuzz_target_1/` Crashes location: `fuzz/artifacts/fuzz_target_1/`

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.