Rooba
/
oss-fuzz
mirror of https://github.com/google/oss-fuzz.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OSS-Fuzz - continuous fuzzing for open source software.
3,970 Commits 189 Branches 0 Tags 122 MiB
Shell 27.2%
Python 19.1%
Dockerfile 17.5%
Java 17%
C 7.2%
Other 11.8%
Go to file
Sebastian Rasmussen 65390a9774
[ghostscript] Relicense target fuzzer under Apache 2.0 license. (#3440) 
When contributed to OSS-fuzz the Ghostscript target fuzzer was
licensed under a "BSD-style" license, referring to a LICENSE file
that actually contained an Apache 2.0 license! Recently the OSS-fuzz
project has added a presubmit check that validates the license of
each project's target fuzzer, causing the Ghostscript target fuzzer
to now fail the test. The Ghostscript target fuzzer therefore needs
to be relicensed under Apache 2.0.

This commit relicenses the existing target fuzzer code under
Apache 2.0 so that the Ghostscript target fuzzer code will pass
OSS-fuzz's presubmit checks allowing for further development.
 		2020-02-28 12:32:13 -08:00
docs Bump nokogiri from 1.10.4 to 1.10.8 in /docs (#3430) 2020-02-26 11:51:08 +11:00
infra [CIFuzz] Adding dry_run mode to check_build (#3444) 2020-02-28 09:41:44 -08:00
projects [ghostscript] Relicense target fuzzer under Apache 2.0 license. (#3440) 2020-02-28 12:32:13 -08:00
.gitignore [infra] replacing wget with ADD where possible 2016-12-28 14:09:09 -08:00
.pylintrc Merge contradictory indent directives (#3226) 2020-01-13 09:34:28 -08:00
.style.yapf [infra] Add presubmit script (#3196) 2020-01-10 10:19:42 -08:00
.travis.yml [Infra] Add tests to presubmit (#3405) 2020-02-21 08:47:13 -08:00
CONTRIBUTING.md Fix hyperlink markdown (#2926) 2019-10-08 10:48:41 -07:00
LICENSE Create LICENSE 2016-10-03 12:24:25 -07:00
README.md [docs] Dummy change in the README just to test something. 2020-02-06 10:34:57 -08:00
oss-fuzz.iml Add jekyll generator for docs. (#2660) 2019-08-06 13:29:19 -07:00

README.md

OSS-Fuzz: Continuous Fuzzing for Open Source Software

Fuzz testing is a well-known technique for uncovering programming errors in software. Many of these detectable errors, like buffer overflow, can have serious security implications. Google has found thousands of security vulnerabilities and stability bugs by deploying guided in-process fuzzing of Chrome components, and we now want to share that service with the open source community.

In cooperation with the Core Infrastructure Initiative, OSS-Fuzz aims to make common open source software more secure and stable by combining modern fuzzing techniques with scalable, distributed execution.

We support the libFuzzer and AFL fuzzing engines in combination with Sanitizers, as well as ClusterFuzz, a distributed fuzzer execution environment and reporting tool.

Currently, OSS-Fuzz supports C/C++, Rust, and Go code. Other languages supported by LLVM may work too. OSS-Fuzz supports fuzzing x86_64 and i386 builds.

Overview

OSS-Fuzz process diagram

Documentation

Read our detailed documentation to learn how to use OSS-Fuzz.

Trophies

As of January 2020, OSS-Fuzz has found over 16,000 bugs in 250 open source projects.

Blog posts