Add security disclosure policy - #111
Merged
truthixify merged 2 commits intoJul 29, 2026
Merged
Conversation
- Add reference/security-disclosure.mdx with full policy: contact, in-scope, response SLA, severity definitions, coordinated disclosure terms, safe-harbor, and bounty table - Add SECURITY.md for repo root with summary and link to full doc - Register reference/security-disclosure in docs.json navigation
|
@brooksdevon001-star Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Merged. Security disclosure page has been on the list forever, glad this lands. Appreciated. |
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.
Add security vulnerability disclosure policy
Researchers who find a bug currently have no documented channel to report it. This PR adds the
missing policy so disclosure can happen responsibly and privately.
Changes
(TEE/key derivation, smart contracts, SDK, API, protocol crypto), response SLA, severity
definitions, 90-day coordinated disclosure window, safe-harbor language, and a discretionary
USDC bounty table ($250–$20k by severity)
bounty) and a link to the full policy; copy this into each repo root
Reference navigation group
Review checklist for whoever holds the security email
closes Coordinated disclosure guide #84