Repository navigation
docs: update SECURITY.md to use private vulnerability reporting - #290
Merged
Merged
Conversation
Stop asking reporters to open public issues for vulnerabilities. Point them to GitHub private vulnerability reporting and security@getstream.io instead, and describe how fixes are disclosed through GitHub security advisories. Refs CHA-7005 Co-Authored-By: Claude Opus 5.5 <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
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.
Updates
SECURITY.mdso vulnerabilities are reported privately.security. A public issue discloses the vulnerability before a fix is available.Same policy as the new
SECURITY.mdfiles in the generated server SDKs. Part of the SDK security hardening work (CHA-7005).Docs-only change, no code affected.
🤖 Generated with Claude Code
Note
Low Risk
Documentation-only change to security reporting policy; no application code or runtime behavior is affected.
Overview
Updates
SECURITY.mdto require private vulnerability reporting and align with other Stream server SDKs.Reporters are told not to use public issues, discussions, or PRs; the old option to open a tagged public issue is removed. Reporting now goes through GitHub private vulnerability reporting (Security tab) or security@getstream.io.
The doc adds guidance on what to include (package, versions, impact, reproduction), a Disclosure section (fixes via releases and GitHub security advisories for Dependabot/scanners), and Supported Versions (fixes on latest SDK, discretion for older majors).
Reviewed by Cursor Bugbot for commit 9b86770. Bugbot is set up for automated code reviews on this repo. Configure here.