oss-fuzz/projects/libyaml/project.yaml

homepage: https://github.com/yaml/libyaml
primary_contact: "sigmavirus24@gmail.com"
auto_ccs:
  - "alex.gaynor@gmail.com"
fuzzing_engines:
  - libfuzzer
  - afl
  - dataflow
sanitizers:
  - address
  - dataflow
  - memory
  - undefined
architectures:
  - x86_64
  - i386
Propose libyaml as a project (#107) 2016-12-01 21:36:00 +00:00			`homepage: https://github.com/yaml/libyaml`
Add myself to the list of auto CCs for libyaml (#521) * Add myself to the list of auto CCs for libyaml As the lead maintainer of libyaml, it would be helpful to get CC'd on any findings of OSS Fuzz. * Update project.yaml 2017-04-06 16:57:18 +00:00			`primary_contact: "sigmavirus24@gmail.com"`
			`auto_ccs:`
			`- "alex.gaynor@gmail.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`