Skip to content
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.

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

Remove license and update security scope #1

Merged
merged 3 commits into from
May 8, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
21 changes: 0 additions & 21 deletions LICENSE

This file was deleted.

13 changes: 7 additions & 6 deletions SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,21 +22,22 @@ Please first submit the vulnerability you discovered using the instructions in
you may share the details with third parties after either of the following,
whichever is sooner:

- the vulnerability has been fixed and the Celestia program owner has provided
- the vulnerability has been fixed and the security program owner has provided
permission for you to disclose it; or
- 120 days after you submit the vulnerability

### Scope

The scope of this security policy applies to the code repositories under the
[@celestiaorg](https://github.com/celestiaorg) and any related infrastructure.
[@rollkit](https://github.com/rollkit) Github org and any related
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: should be GitHub

infrastructure.

### Rewards

Celestia Labs has no formal reward policy and researchers should not expect a
reward for discovering a vulnerability. Celestia Labs is nonetheless grateful
for all legitimate discoveries of vulnerabilities, and is happy to acknowledge
the vulnerability and the researchers after a fix has been widely deployed.
We have no formal reward policy and researchers should not expect a reward for
discovering a vulnerability. We are nonetheless grateful for all legitimate
discoveries of vulnerabilities, and is happy to acknowledge the vulnerability
and the researchers after a fix has been widely deployed.

### Official Communication Channel

Expand Down