https://github.com/google/fuzzer-test-suite

Set of tests for fuzzing engines
https://github.com/google/fuzzer-test-suite

Last synced: 9 days ago
JSON representation

Set of tests for fuzzing engines

• Host: GitHub
• URL: https://github.com/google/fuzzer-test-suite
• Owner: google
• License: apache-2.0
• Created: 2016-10-07T05:32:34.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2021-08-25T17:25:26.000Z (about 3 years ago)
• Last Synced: 2024-08-01T09:23:49.164Z (3 months ago)
• Language: C
• Homepage:
• Size: 2.72 MB
• Stars: 1,419
• Watchers: 81
• Forks: 276
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING
  • License: LICENSE

Awesome Lists containing this project

README

        
# fuzzer-test-suite

:zap: **NOTE: For most use cases, fuzzer-test-suite is superseded by [FuzzBench](https://github.com/google/fuzzbench). 

We recommend using FuzzBench for all future fuzzer benchmarking. 

FuzzBench is based on many of the same ideas as FTS, such as realistic benchmarks (it actually uses some benchmarks from FTS) but has many improvements such as a free service and a design that makes adding new fuzzers and new benchmarks easier.**

This is a set of tests (benchmarks) for fuzzing engines (fuzzers).

The goal of this project is to have a set of fuzzing benchmarks derived from real-life

libraries that have interesting bugs, hard-to-find code paths, or other

challenges for bug finding tools.

The current version supports [libFuzzer](http://libFuzzer.info) and

[AFL](http://lcamtuf.coredump.cx/afl/).  In future versions we may support

other fuzzing engines.

# See also

* [AddressSanitizer](http://clang.llvm.org/docs/AddressSanitizer.html)

# Contributing

See [CONTRIBUTING](CONTRIBUTING) first. 

If you want to add one more benchmark to the test suite,

simply mimic one of the existing benchmarks and send the pull request. 

# Disclaimer

This is not an official Google product.