-
-
Notifications
You must be signed in to change notification settings - Fork 228
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
af285ef
commit 73a4a2a
Showing
2 changed files
with
31 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Security Policy 🚨 | ||
|
||
## Reporting a Vulnerability 🐞 | ||
|
||
The `Proyecto 26` team and community take all security bugs in `react-native-inappbrowser-reborn` seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions. | ||
|
||
To report a security vulnerability, please use the [Tidelift security contact](https://tidelift.com/security). Tidelift will coordinate the fix and disclosure. | ||
|
||
The `Proyecto 26` team will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance. | ||
|
||
Report security bugs in third-party modules to the person or team maintaining the module. | ||
|
||
## Disclosure Policy 📢 | ||
|
||
When the security team receives a security bug report, they will assign it to a primary handler. This person will coordinate the fix and release process, | ||
involving the following steps: | ||
|
||
* Confirm the problem and determine the affected versions. | ||
* Audit code to find any potential similar problems. | ||
* Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible. | ||
|
||
## Comments on this Policy ✍ | ||
|
||
If you have suggestions on how this process could be improved please submit a pull request. | ||
|
||
## Security Is Everyone's Responsibility 🌐 | ||
|
||
Thank you for making the world a better place for everyone! 🙏 |