| Mike Aizatsky | 3986fa3 | 2016-09-14 09:44:10 -0700 | [diff] [blame] | 1 | # oss-fuzz |
| 2 | |
| Mike Aizatsky | 45c194e | 2016-09-14 10:09:15 -0700 | [diff] [blame] | 3 | oss-fuzz is an effort to apply coverage-guided software fuzzing on scale to test open source software. It grew out of Chrome in-process fuzzing effort ([Blog Post](https://security.googleblog.com/2016/08/guided-in-process-fuzzing-of-chrome.html), [Project Page](https://chromium.googlesource.com/chromium/src/testing/libfuzzer/)). |
| Mike Aizatsky | 3986fa3 | 2016-09-14 09:44:10 -0700 | [diff] [blame] | 4 | |
| 5 | |
| 6 | *Project Status*: The project currently is in early stage. We focus on libFuzzer first. Documentation and smoothing the process is our main priority. |
| 7 | |
| 8 | ## Documentation |
| 9 | |
| 10 | * [New Library Guide](docs/new_library.md) walks through steps necessary to add fuzzers to an open source project. |
| 11 | * [Chrome's Efficient Fuzzer Guide](https://chromium.googlesource.com/chromium/src/testing/libfuzzer/+/HEAD/efficient_fuzzer.md) while contains some chrome-specifics, is an excellent documentation on making your fuzzer better. |
| 12 | |
| 13 | |
| 14 | ## References |
| 15 | * [libFuzzer](http://llvm.org/docs/LibFuzzer.html) |
| 16 | * [Chromium In-Process Fuzzing Project Page](https://chromium.googlesource.com/chromium/src/testing/libfuzzer/) |
| 17 | |