-
-
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
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 | ||
|
||
Use this section to tell people about which versions of your project are | ||
currently being supported with security updates. | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 1.x.x | :white_check_mark: | | ||
|
||
|
||
## Reporting a Vulnerability | ||
|
||
If you believe you've found a security vulnerability in this package, please follow these steps to report it responsibly: | ||
|
||
1. **Privately Notify the Maintainers**: Do not disclose the vulnerability publicly. Instead, email the maintainers directly at [[email protected]] with details of the vulnerability. Please include the word "SECURITY" in the subject line. | ||
|
||
2. **Provide Detailed Information**: When reporting the vulnerability, include as much detail as possible, including: | ||
- Description of the vulnerability | ||
- Steps to reproduce the vulnerability | ||
- Affected versions of the package | ||
- Any potential impact or exploit scenarios | ||
|
||
3. **Be Patient**: We take security vulnerabilities seriously and will investigate promptly. You can expect an initial response within 1 day acknowledging your report and outlining the next steps in the process. | ||
|
||
4. **Cooperate Confidentially**: If we confirm the vulnerability, we may request further information or assistance from you. Please cooperate with us confidentially throughout the process. | ||
|
||
5. **Public Disclosure**: Once a fix is available, we'll work with you to determine an appropriate timeline for public disclosure. This ensures that users have enough time to update their systems before details of the vulnerability are made public. | ||
|
||
Thank you for helping to keep our package and its users safe! |