pesde-pkg/pesde
1
1
Fork 0
mirror of https://github.com/pesde-pkg/pesde.git synced 2025-04-10 22:00:55 +01:00
Code Issues Projects Releases Packages Wiki Activity

docs: update security policy

Browse source
This commit is contained in:
daimond113 2025-02-22 22:22:04 +01:00
parent 1b984f2d82
commit cb3c47477a
No known key found for this signature in database
GPG key ID: 640DC95EC1190354
1 changed files with 7 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
SECURITY.md
View file

@ -3,23 +3,26 @@
## Supported Versions ## Supported Versions
As pesde is currently in version 0.x, we can only guarantee security for: As pesde is currently in version 0.x, we can only guarantee security for:
- **The latest minor** (currently 0.5).
- **The latest minor** (currently 0.6).
- **The latest release candidate for the next version**, if available. - **The latest release candidate for the next version**, if available.
When a new minor version is released, the previous version will immediately lose security support. When a new minor version is released, the previous version will immediately lose security support.
> **Note:** This policy will change with the release of version 1.0, which will include an extended support period for versions >=1.0. > **Note:** This policy will change with the release of version 1.0, which will include an extended support period for versions >=1.0.
| Version | Supported | | Version | Supported |
| ------- | ------------------ | | ------- | ------------------ |
| 0.5.x | :white_check_mark: | | 0.6.x | :white_check_mark: |
| < 0.5 | :x: | | < 0.6 | :x: |
## Reporting a Vulnerability ## Reporting a Vulnerability
We encourage all security concerns to be reported at [pesde@daimond113.com](mailto:pesde@daimond113.com), along the following format: We encourage all security concerns to be reported at [pesde@daimond113.com](mailto:pesde@daimond113.com), along the following format:
- **Subject**: The subject must be prefixed with `[SECURITY]` to ensure it is prioritized as a security concern. - **Subject**: The subject must be prefixed with `[SECURITY]` to ensure it is prioritized as a security concern.
- **Content**: - **Content**:
- **Affected Versions**: Clearly specify which are affected by the issue. - **Affected Versions**: Clearly specify which are affected by the issue.
- **Issue Details**: Provide a detailed description of the issue, including reproduction steps and/or a simple example, if applicable. - **Issue Details**: Provide a detailed description of the issue, including reproduction steps and/or a simple example, if applicable.
We will try to respond as soon as possible. We will try to respond as soon as possible.