Skip to content

Commit

Permalink
create SECURITY.md
Browse files Browse the repository at this point in the history
  • Loading branch information
isakruas authored Apr 22, 2024
1 parent f98f0e2 commit dee7ecb
Showing 1 changed file with 40 additions and 0 deletions.
40 changes: 40 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
# 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 |
| ------- | ------------------ |
| 0.0.1 | :white_check_mark: |
| 0.0.1a0 | :x: |
| 0.0.1.dev4 | :x: |
| 0.0.1.dev3 | :x: |
| 0.0.1.dev2 | :x: |
| 0.0.1.dev1 | :x: |
| 0.0.1.dev0 | :x: |


## Reporting a Vulnerability

Use this section to tell people how to report a vulnerability.

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.

To report a vulnerability, please send an email to [isakruas@gmail.com](mailto:isakruas@gmail.com) with the following details:

- **Subject:** Security Vulnerability Report
- **Description:** Provide a detailed description of the vulnerability, including any relevant information about its impact and potential exploitation.
- **Steps to Reproduce:** If possible, include step-by-step instructions to reproduce the vulnerability.
- **Affected Versions:** Specify which versions of the project are affected by the vulnerability.
- **Proof of Concept:** If applicable, include any proof of concept or demonstration code to illustrate the vulnerability.

Upon receiving your report, we will acknowledge its receipt within 48 hours. Our team will then investigate the reported vulnerability and provide an initial assessment within 7 days. We will keep you informed of our progress and any updates throughout the process.

If the reported vulnerability is confirmed, we will work diligently to develop and release a security patch. Once the patch is ready, we will notify you and coordinate the disclosure of the vulnerability details.

We kindly request that you refrain from disclosing the vulnerability publicly until we have had sufficient time to address it. We aim to provide timely updates and transparent communication throughout the resolution process.

Thank you for helping us maintain the security of our project.

0 comments on commit dee7ecb

Please sign in to comment.