-
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
1 parent
2036dd9
commit 3e0cafc
Showing
1 changed file
with
46 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,46 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
We currently support the following versions of Melodica for security updates: | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| latest | ✅ | | ||
| older versions | ❌ | | ||
|
||
Please make sure to update to the latest version to benefit from the latest security patches and updates. | ||
|
||
## Reporting a Vulnerability | ||
|
||
We take security vulnerabilities seriously. If you discover a security issue within Melodica, please follow these steps to report it responsibly: | ||
|
||
1. **Do not open a public issue**. Reporting vulnerabilities publicly can lead to misuse of the information. | ||
2. Instead, please email the maintainer(s) at: | ||
``` | ||
[email protected] | ||
``` | ||
3. In your email, include: | ||
- A description of the vulnerability. | ||
- Detailed steps to reproduce the issue, if applicable. | ||
- Any potential impact you believe the vulnerability may have on the project. | ||
|
||
### Response Process | ||
|
||
Upon receiving a report, we will: | ||
|
||
1. Acknowledge receipt of your vulnerability report. | ||
2. Begin the process of validating and reproducing the issue. | ||
3. Work on a fix, keeping you updated throughout the process. | ||
4. Release a patch to address the vulnerability. | ||
5. Publicly acknowledge and thank the reporter (if desired) once the vulnerability is resolved. | ||
|
||
### Security Updates | ||
|
||
We will periodically update Melodica with security patches, and encourage users to stay on the latest release for optimal security. Major vulnerabilities and their fixes will be documented in our release notes. | ||
|
||
## Responsible Disclosure | ||
|
||
We kindly request that reporters follow responsible disclosure practices, giving us the opportunity to address and patch vulnerabilities before sharing details publicly. | ||
|
||
Thank you for helping us keep Melodica secure for everyone! |