| 1 |
# Security Policy |
| 2 |
|
| 3 |
## Supported Versions |
| 4 |
|
| 5 |
We provide security updates for the last stable release of Modules and for a |
| 6 |
given list of stable releases listed below. Security updates will be made |
| 7 |
available as patch (`x.y.1`, `x.y.2`, etc.) releases. |
| 8 |
|
| 9 |
| Version | Supported | |
| 10 |
| ------------ | ------------------ | |
| 11 |
| 5.6.x | :white_check_mark: | |
| 12 |
| > 5.3, < 5.6 | :x: | |
| 13 |
| 5.3.x | :white_check_mark: | |
| 14 |
| > 4.5, < 5.3 | :x: | |
| 15 |
| 4.5.x | :white_check_mark: | |
| 16 |
| < 4.5 | :x: | |
| 17 |
|
| 18 |
## Reporting a Vulnerability |
| 19 |
|
| 20 |
You can report a vulnerability using GitHub's private reporting feature: |
| 21 |
|
| 22 |
1. Go to [github.com/envmodules/modules/security](https://github.com/envmodules/modules/security). |
| 23 |
2. Click "Report a vulnerability" in the upper right corner of that page. |
| 24 |
3. Fill out the form and submit your draft security advisory. |
| 25 |
|
| 26 |
More details are available in |
| 27 |
[GitHub's docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability). |
| 28 |
|
| 29 |
You can expect to hear back about security issues within five working days. If |
| 30 |
your security issue is accepted, we will do our best to release a fix within |
| 31 |
two weeks. If fixing the issue will take longer than this, we will discuss |
| 32 |
timeline options with you. |