-
Notifications
You must be signed in to change notification settings - Fork 0
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
23 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,23 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 0.1.x | :white_check_mark: | | ||
|
||
## Reporting a Vulnerability | ||
|
||
To report a vulnerability, please follow these steps: | ||
|
||
1. **Contact Us**: Send an email to the maintainer or open an issue with details of the vulnerability. | ||
2. **Details to Include**: Provide as much information as possible, including: | ||
- A detailed description of the vulnerability. | ||
- Steps to reproduce the issue. | ||
- Any potential impacts of the vulnerability. | ||
- Any suggestions for a fix, if available. | ||
3. **Acknowledgment**: You will receive an acknowledgment of your report within 72 hours. | ||
4. **Update Frequency**: We will provide updates on the status of the vulnerability at least once every 5 days. | ||
5. **Resolution**: If the vulnerability is accepted, we will work on a fix and release an update as soon as possible. If it is declined, we will provide an explanation. | ||
|
||
We appreciate your efforts in keeping our project secure. |