docs(security): record OSS-Fuzz upstream rejection in OSS_FUZZ.md#463
Open
CryptoJones wants to merge 1 commit into
Open
docs(security): record OSS-Fuzz upstream rejection in OSS_FUZZ.md#463CryptoJones wants to merge 1 commit into
CryptoJones wants to merge 1 commit into
Conversation
OSS_FUZZ.md still read as a forward-looking integration plan even though google/oss-fuzz#15545 was declined 2026-05-26 (Google does not accept forks) and the .github/oss-fuzz/ wrapper was removed in #84. The other project-state docs were reconciled in #83; this one was missed. - Add a status banner quoting the rejection and re-scoping to in-tree fuzzing. - Fix the dead .github/oss-fuzz/ scaffold reference (removed in #84). - Reframe the submission checklist as historical: build/wrapper items done, the upstream-build item marked won't-happen. - Reframe the maintenance commitment from "keep the OSS-Fuzz build green" to keeping the in-tree harnesses building (they bit-rotted once, repaired in cad859a). Docs-only. Follow-up to closing #450. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Follow-up to closing #450.
docs/security/OSS_FUZZ.mdstill read as a forward-looking plan to stand up a Google-hosted OSS-Fuzz project, even though google/oss-fuzz#15545 was declined on 2026-05-26 (Google collaborator DavidKorczynski: forks aren't a good OSS-Fuzz match) and the.github/oss-fuzz/wrapper was removed in #84. The other project-state docs (CHANGELOG, SprintPlanning) were reconciled in #83; this doc was missed.Changes (docs-only):
.github/oss-fuzz/scaffold reference (those files were removed in chore(rec-13/14): remove dead .github/oss-fuzz/ wrapper #84; preserved in git history).cad859a).🤖 Generated with Claude Code