oss-fuzz/projects/zlib/project.yaml

homepage: "http://www.zlib.net/"
primary_contact: "glennrp@gmail.com"
auto_ccs:
  - "sebpop@gmail.com"
  - "cblume@google.com"
fuzzing_engines:
  - libfuzzer
  - afl
  - dataflow
sanitizers:
  - address
  - dataflow
  - memory
  - undefined
architectures:
  - x86_64
  - i386
[infra] adding target.yaml files (#92) Fixes issue #89 2016-11-21 23:05:13 +00:00			`homepage: "http://www.zlib.net/"`
add glennrp as project contact (has been approved by mark adler, project owner) (#853) 2017-09-23 21:57:35 +00:00			`primary_contact: "glennrp@gmail.com"`
[zlib] add fuzzers (#1780) 2018-11-07 18:20:02 +00:00			`auto_ccs:`
			`- "sebpop@gmail.com"`
Add myself to autocc of zlib (#2152) I wrote many of the zlib fuzzers that are used in Chromium. I also just submitted a pull request for those to go to upstream zlib. It would be handy for me to be notified when the fuzzers find something in zlib. This commit adds myself to the autocc of zlib. 2019-02-08 23:38:51 +00:00			`- "cblume@google.com"`
Enable dataflow for 9 projects written in C (#1632). 2019-06-28 20:59:03 +00:00			`fuzzing_engines:`
			`- libfuzzer`
			`- afl`
			`- dataflow`
Enable msan experimental on some projects. (#514) 2017-04-05 00:13:59 +00:00			`sanitizers:`
			`- address`
Enable dataflow for 9 projects written in C (#1632). 2019-06-28 20:59:03 +00:00			`- dataflow`
Remove experimental flag from tested msan projects (#473). (#517) 2017-04-05 16:58:03 +00:00			`- memory`
Enable msan experimental on some projects. (#514) 2017-04-05 00:13:59 +00:00			`- undefined`
Enable i386 fuzzing on 18 projects (#2748) Maintainers who own these projects: If you don't want i386 fuzzing, feel free to disable. I figured i386 fuzzing is generally desirable since it can find more bugs but most projects won't switch because of inertia. 2019-08-22 15:44:03 +00:00			`architectures:`
			`- x86_64`
			`- i386`