-
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
22 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,22 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 0.0.4.8 | :white_check_mark: | | ||
| older | :x: | | ||
|
||
## Reporting a Vulnerability | ||
|
||
To report a vulnerability, please follow these steps: | ||
|
||
1. **Contact Information**: Send an email to [[email protected]](mailto:[email protected]) with details about the vulnerability. Include any relevant information such as the affected version, potential impact, and steps to reproduce. | ||
|
||
2. **Response Timeline**: We aim to acknowledge the report within 48 hours and provide regular updates every two weeks until the issue is resolved. | ||
|
||
3. **Next Steps**: Once a report is validated, we will work on a fix and communicate an expected release timeline. If the vulnerability is declined or does not qualify as a security risk, we will provide an explanation. | ||
|
||
4. **Confidentiality**: We request that vulnerability details remain confidential until a fix is publicly released. | ||
|
||
Thank you for helping us keep our project secure! |