chore(docs): update security email - #3379
Merged
Merged
Conversation
nkaradzhov
force-pushed
the
update-security-mail
branch
from
July 29, 2026 09:43
9154719 to
265cea3
Compare
PavelPashov
approved these changes
Jul 29, 2026
PavelPashov
requested changes
Jul 29, 2026
Comment on lines
+20
to
+21
| For those averse to using our chosen platform, we will also accept reports directly | ||
| via GitHub's "Report a Vulnerability". |
Contributor
There was a problem hiding this comment.
Do we have this enabled?
nkaradzhov
force-pushed
the
update-security-mail
branch
from
July 29, 2026 09:52
265cea3 to
b1e6972
Compare
PavelPashov
approved these changes
Jul 29, 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
2 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.
Description
Checklist
npm testpass with this change (including linting)?Note
Low Risk
Documentation-only change to security reporting contacts; no runtime or security logic affected.
Overview
Reporting a Vulnerability now directs researchers to Redis’s Vulnerability Disclosure Program instead of emailing
redis@redis.io, with brief rationale (review process, response times, paid engagements).Direct security questions are pointed to security@redis.com via mailto link.
Reviewed by Cursor Bugbot for commit b1e6972. Bugbot is set up for automated code reviews on this repo. Configure here.