-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Showing
4 changed files
with
46 additions
and
1 deletion.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
--- | ||
name: Pull Request | ||
title: 'short description' | ||
--- | ||
|
||
**Describe the Pull Request** | ||
A clear and concise description of what the Pull Request is and link to existing issue. | ||
|
||
- [ ] I read contribution guidelines | ||
- [ ] Pull request introduces a BC-Break | ||
- [ ] Pull request is covered by tests | ||
- [ ] Pull request is properly documented in docs |
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,29 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
| Version | Supported | | ||
|---------| ------------------ | | ||
| >= 0.5 | :heavy_check_mark: | | ||
|
||
|
||
## Reporting Potential Security Issues | ||
If you have encountered a potential security vulnerability in this project, please report it to us at [TODO: email address]. We will work with you to verify the vulnerability and patch it. | ||
|
||
When reporting issues, please provide the following information: | ||
|
||
* Component(s) affected | ||
* A description indicating how to reproduce the issue | ||
* A summary of the security vulnerability and impact | ||
* We request that you contact us via the email address above and give the project contributors a chance to resolve the vulnerability and issue a new release prior to any public exposure; this helps protect the project's users, and provides them with a chance to upgrade and/or update in order to protect their applications. | ||
|
||
For sensitive email communications, please use our PGP key. | ||
|
||
## Policy | ||
If we verify a reported security vulnerability, our policy is: | ||
|
||
* We will patch the current release branch, as well as the immediate prior minor release branch. | ||
|
||
* After patching the release branches, we will immediately issue new security fix releases for each patched release branch. | ||
|
||
* A security advisory will be released on the project website detailing the vulnerability, as well as recommendations for end-users to protect themselves. Security advisories will be listed at [TODO: website], as well as via a feed (which is also present in the website head for easy feed discovery). |
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