Skip to content

fix: extend bug bounty response SLA to prevent breaches #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
codeboost-tr wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: extend bug bounty response SLA to prevent breaches #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dex-tegro-finance/bug-bounty.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Describe the vulnerability you found in as much detail as possible and provide u

### What happens after the error report?

Our security experts will carefully review your report and contact you within two business days to discuss the problem:
Our security experts will carefully review your report and contact you within seven business days to discuss the problem:

* Under what circumstances did you discover the vulnerability?
* The next steps are also discussed if the vulnerability report is still relevant or was found by you for the first time.
Expand Down
2 changes: 1 addition & 1 deletion tegro-wallet/bug-bounty.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Describe the vulnerability you found in as much detail as possible and provide u

### What happens after the error report?

Our security experts will carefully review your report and contact you within two business days to discuss the problem:
Our security experts will carefully review your report and contact you within seven business days to discuss the problem:

* Under what circumstances did you discover the vulnerability? 
* The next steps are also discussed if the vulnerability report is still relevant or was found by you for the first time.
Expand Down