|
1 | | -# Security Policy |
| 1 | +# Security Policy |
2 | 2 |
|
3 | | -## Supported Versions |
| 3 | +## Supported Versions |
4 | 4 |
|
5 | | -At the moment, Avogadro2 is in beta release. As such, we can most easily support |
6 | | -security updates on the most recent release and current nightly snapshots. |
7 | | -We will work with distributions (e.g., Ubuntu, FreeBSD, etc.) to provide security |
| 5 | +At the moment, Avogadro2 is in beta release. As such, we can most easily support |
| 6 | +security updates on the most recent release and current nightly snapshots. |
| 7 | +We will work with distributions (e.g., Ubuntu, FreeBSD, etc.) to provide security |
8 | 8 | patches for widely used long-term-support OS. |
9 | 9 |
|
10 | | -| Version | Supported | |
11 | | -| ------- | ------------------ | |
| 10 | +| Version | Supported | |
| 11 | +| ------- | ------------------ | |
| 12 | +| 1.99.x | :white_check_mark: | |
12 | 13 | | 1.98.x | :white_check_mark: | |
13 | | -| 1.97.x | :white_check_mark: | |
14 | | -| < 1.97 | :x: | |
| 14 | +| < 1.98 | :x: | |
15 | 15 |
|
16 | | -## Reporting a Vulnerability |
| 16 | +## Reporting a Vulnerability |
17 | 17 |
|
18 | | -We currently support private security vulnerability reporting through our |
19 | | -[GitHub](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability) |
20 | | -pages. We will work to verify the security vulnerability within 14 days |
| 18 | +We currently support private security vulnerability reporting through our |
| 19 | +[GitHub](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability) |
| 20 | +pages. We will work to verify the security vulnerability within 14 days |
21 | 21 | and a patch or new release within 30 days of reporting. |
0 commit comments