[INFOSEC-634] Add security policy - #393
Merged
Merged
Conversation
jonho-gif
approved these changes
Sep 23, 2026
gokulhost
approved these changes
Sep 24, 2026
bhargavirao24
force-pushed
the
add-security-policy
branch
from
October 1, 2026 18:39
083544f to
6820b13
Compare
pritam-gembali
approved these changes
Oct 1, 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
4 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
Adds a
SECURITY.mdfile so security researchers have clear instructions for privately reporting vulnerabilities in BitGoWASM.The policy:
security@bitgo.comTesting
Not applicable. This is a documentation-only change.
Tracking
INFOSEC-634: Publish SECURITY.md for public repositories