Remove fork-local SECURITY.md to inherit Mixpanel org security policy - #19
Open
scotmatson wants to merge 1 commit into
Open
Remove fork-local SECURITY.md to inherit Mixpanel org security policy#19scotmatson wants to merge 1 commit into
scotmatson wants to merge 1 commit into
Conversation
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.
What
Removes this repository's
SECURITY.md.Why
This fork currently ships the upstream rrweb community security policy, which routes vulnerability reports to rrweb's GitHub Security page and the
rrweb-security@googlegroups.comcommunity group — not to Mixpanel. On a public, Mixpanel-maintained fork, that means security reports can bypass Mixpanel's security team entirely.What happens after this is merged
GitHub serves default community health files from an organization's
.githubrepository to any repo that does not define its own. Mixpanel's org-wide policy lives here:➡️ https://github.com/mixpanel/.github/blob/main/SECURITY.md
Because this repository will no longer have its own
SECURITY.md, GitHub will automatically apply Mixpanel's org-wideSECURITY.mdas this repo's policy. Vulnerability reports will then route to Mixpanel's disclosure channels (security@mixpanel.com/ bug bounty) with proper scope guidance — no per-repo file required.If a repository-specific policy is ever needed, adding a
SECURITY.mdback to this repo will override the org default (GitHub uses the repo's own file when present, and falls back tomixpanel/.githubotherwise).