-
Notifications
You must be signed in to change notification settings - Fork 298
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
ff48b9c
commit 73b76a5
Showing
1 changed file
with
21 additions
and
13 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 |
---|---|---|
|
@@ -2,20 +2,28 @@ | |
|
||
## Supported Versions | ||
|
||
Use this section to tell people about which versions of your project are | ||
currently being supported with security updates. | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 5.1.x | :white_check_mark: | | ||
| 5.0.x | :x: | | ||
| 4.0.x | :white_check_mark: | | ||
| < 4.0 | :x: | | ||
We release security updates for the latest version of **AlDente** here: https://github.com/AppHouseKitchen/AlDente-Charge-Limiter/releases | ||
|
||
## Reporting a Vulnerability | ||
|
||
Use this section to tell people how to report a vulnerability. | ||
We take the security of our software seriously. If you discover a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner. | ||
|
||
**How to Report** | ||
|
||
- **Email:** Please send an email to [[email protected]](mailto:[email protected]). | ||
- **Subject Line:** Use a clear and descriptive subject line, such as "Security Vulnerability in AlDente-Charge-Limiter". | ||
- **Content:** Provide a detailed description of the vulnerability, including steps to reproduce it, the potential impact, and any suggested fixes. | ||
|
||
**What to Expect** | ||
|
||
- **Acknowledgment:** We will acknowledge receipt of your report within 48 hours. | ||
- **Investigation:** Our team will investigate the issue and work on a fix. | ||
- **Updates:** We will keep you informed about the progress of the investigation and remediation. | ||
- **Disclosure:** Once the vulnerability is resolved, we will issue a patch and publicly disclose the issue, crediting you for the discovery if you wish. | ||
|
||
**Guidelines** | ||
|
||
- **Confidentiality:** Please do not disclose the vulnerability publicly until we have addressed it. | ||
- **Legal:** You must not violate any laws or breach any agreements in the course of discovering and reporting vulnerabilities. | ||
|
||
Tell them where to go, how often they can expect to get an update on a | ||
reported vulnerability, what to expect if the vulnerability is accepted or | ||
declined, etc. | ||
Thank you for helping us keep **AlDente** safe and secure for everyone! |