-
Notifications
You must be signed in to change notification settings - Fork 5
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
1 changed file
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
The following table outlines the versions of our project that are currently supported with security updates: | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 16.0.x | :white_check_mark: | | ||
| < 16.0 | :x: | | ||
|
||
## Reporting a Vulnerability | ||
|
||
We encourage users to report security vulnerabilities to help us maintain the safety and integrity of our project. Please follow these steps to report a vulnerability: | ||
|
||
1. **Open an Issue:** Navigate to the [Issues](https://github.com/helsenorge/refero/issues) section of our repository and create a new issue. | ||
|
||
2. **Use the "Security" Label:** When creating the issue, apply the "Security" label to categorize it appropriately. | ||
|
||
3. **Provide Detailed Information:** Include comprehensive details about the vulnerability, such as: | ||
- Steps to reproduce the issue | ||
- Potential impact | ||
- Any suggested solutions or mitigations | ||
|
||
4. **Response Time:** Our team will acknowledge and begin investigating reported vulnerabilities within one week during business days. We will keep you informed about the progress and any actions taken. | ||
|
||
5. **Confidentiality:** To protect our users, please refrain from publicly disclosing the vulnerability until we have addressed it and released a fix. | ||
|
||
By adhering to this process, you assist us in ensuring the security and reliability of our project. | ||
|
||
*Note: This policy is based on best practices for vulnerability management and coordinated disclosure.* [Learn more](https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository) |