File: SECURITY.md

package info (click to toggle)
modules 5.6.1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 23,036 kB
  • sloc: exp: 79,659; sh: 6,142; tcl: 5,900; makefile: 1,492; ansic: 474; python: 265; csh: 202; perl: 47; ruby: 44; lisp: 13
file content (32 lines) | stat: -rw-r--r-- 1,340 bytes parent folder | download
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
# Security Policy

## Supported Versions

We provide security updates for the last stable release of Modules and for a
given list of stable releases listed below. Security updates will be made
available as patch (`x.y.1`, `x.y.2`, etc.) releases.

| Version      | Supported          |
| ------------ | ------------------ |
| 5.6.x        | :white_check_mark: |
| > 5.3, < 5.6 | :x:                |
| 5.3.x        | :white_check_mark: |
| > 4.5, < 5.3 | :x:                |
| 4.5.x        | :white_check_mark: |
| < 4.5        | :x:                |

## Reporting a Vulnerability

You can report a vulnerability using GitHub's private reporting feature:

1. Go to [github.com/envmodules/modules/security](https://github.com/envmodules/modules/security).
2. Click "Report a vulnerability" in the upper right corner of that page.
3. Fill out the form and submit your draft security advisory.

More details are available in
[GitHub's docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability).

You can expect to hear back about security issues within five working days. If
your security issue is accepted, we will do our best to release a fix within
two weeks. If fixing the issue will take longer than this, we will discuss
timeline options with you.