Add an 'OSS-Fuzz for CPython' overview#1801
Open
StanFromIreland wants to merge 2 commits into
Open
Conversation
Documentation build overview
4 files changed+ testing/oss-fuzz/index.html± index.html± testing/index.html± versions/index.html |
hugovk
approved these changes
May 15, 2026
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
vstinner
approved these changes
May 15, 2026
Member
vstinner
left a comment
There was a problem hiding this comment.
LGTM. Thanks. That's a great overflow of OSS-Fuzz for CPython.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The page serves as a general overview. I left the details about how to actually add a new target to the docs bundled with them. The process differs for the two projects, and is subject to change in the future so it's best to keep it together.
I'd add @python/fuzzers as a CODEOWNER however the team doesn't have write access here.
Also, CC @vstinner and @serhiy-storchaka (I'd really like to know, would you have found this info helpful for your issue earlier?)