..
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38 | # Security Policy
## Supported Versions
| Version | Supported |
| ------- | --------- |
| 0.2.0 | ❔ |
| 0.1.0 | ✅ |
| < 0.1.0 | ❌ |
## Reporting a Vulnerability
If you discover a security vulnerability, please report it by opening an [issue](https://github.com/Miruro-no-kuon/Miruro-no-Kuon/issues). To help us better understand and address the issue, please follow the template provided when creating a new issue.
### Reporting Process
1. **Open a new issue**: Clearly describe the vulnerability, providing as much detail as possible.
2. **Assessment**: Our team will assess the reported vulnerability and respond when available.
3. **Fix and Release**: If the vulnerability is accepted, we will work on fixing it and release a patch within a reasonable timeframe.
### Expectations
- We will strive to keep you informed about the progress of your reported vulnerability.
- If the vulnerability is accepted, it will be prioritized based on severity.
- If the vulnerability is declined, we will provide a reason for the decision.
- We encourage responsible disclosure, and we appreciate your efforts in keeping our project secure.
## Versioning Scheme
We follow [Semantic Versioning](https://semver.org/) for our releases. Security updates will be applied to the latest minor version of the current major version.
- **Major Version**: Significant changes, possibly breaking backward compatibility.
- **Minor Version**: New features, enhancements, and backward-compatible bug fixes.
- **Patch Version**: Backward-compatible bug fixes only.
## Contact
For any questions or additional information regarding security, please contact [email protected]
|
|
