Document both vulnerability reporting channels - #1088
Merged
Conversation
Wiki claimed GitHub private vulnerability reporting was the only channel, but SECURITY.md documents email-only reporting to contact@karafka.io. Both channels are actually live simultaneously (GitHub PVR confirmed enabled via the repo's API, SECURITY.md confirmed current), so the wiki now lists both instead of just one.
mensfeld
approved these changes
Aug 19, 2026
mensfeld
approved these changes
Aug 19, 2026
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.
Summary
Pro/Compliance-Certifications.mdclaimed vulnerability reporting only happens through GitHub's private vulnerability reporting program, butSECURITY.mddocuments an email-only channel (contact@karafka.io). Per the Redmine discussion, both channels are genuinely live simultaneously - GitHub PVR is confirmed enabled on the repo, and SECURITY.md is confirmed current and unchanged. Updated the wiki to mention both.Per Redmine #44907, following Maciej's proposed wording ("via email OR via GitHub's private vulnerability reporting program").
Scope note
Only the wiki was touched here. Whether
SECURITY.mditself should also mention the GitHub PVR option (currently email-only) was raised as a separate open question in the ticket discussion and left for a separate decision - not done in this PR.Test plan
npm run lint- 0 issues across all 196 files