@@ -7,7 +7,7 @@ This document describes the security policy that applies to this repository.
77Security updates for this repository will be applied the most recent major
88version and its minor versions.
99
10- For example if 2.2.0 is the latest version:
10+ For example, if 2.2.0 is the latest version:
1111
1212| Version | Supported |
1313| ------- | ------------------ |
@@ -17,7 +17,7 @@ For example if 2.2.0 is the latest version:
1717| < 2.0.0 | :x : |
1818
1919However, if the repository has not made a stable release (e.g. the latest
20- release is < v1.0.0) then only the most latest minor version will be patched.
20+ release is < v1.0.0) then only the latest minor version will be patched.
2121
2222## Security Release & Disclosure Process
2323
@@ -46,25 +46,25 @@ It is reasonable to delay disclosure when the bug or the fix is not yet fully
4646understood, the solution is not well-tested, or for vendor coordination. The
4747time frame for disclosure is from immediate (especially if it's already publicly
4848known) to several weeks. For a vulnerability with a straightforward mitigation,
49- we expect report date to disclosure date to be on the order of 14 days.
49+ we expect the report date to disclosure date to be on the order of 14 days.
5050
5151If you know of a publicly disclosed security vulnerability please IMMEDIATELY
5252[ report the vulnerability] ( #reporting-a-vulnerability ) so that the patch,
5353release, and communication process can be started as early as possible.
5454
55- If the reporter does not go through the private disclosure process, the fix and
55+ If the reporter does not go through the private disclosure process, the fix, and
5656release process will proceed as swiftly as possible. In extreme cases you can
5757ask GitHub to delete the issue but this generally isn't necessary and is
5858unlikely to make a public disclosure less damaging.
5959
6060### Security Releases
6161
62- Once a fix is available it will be released, the GitHub Security Advisory made
63- public and announced via project communication channels. Security releases
64- will clearly marked as a security release and include information on which
65- vulnerabilities were fixed. As much as possible this announcement should be
66- actionable, and include any mitigating steps users can take prior to upgrading
67- to a fixed version.
62+ Once a fix is available, it will be released, the GitHub Security Advisory made
63+ public, and the fix release announced via project communication channels.
64+ Security releases will be clearly marked as a security release and include
65+ information on which vulnerabilities were fixed. As much as possible this
66+ announcement should be actionable, and include any mitigating steps users can
67+ take prior to upgrading to a fixed version.
6868
6969Fixes will be applied in patch releases to all [ supported
7070versions] ( #supported-versions ) and all fixed vulnerabilities will be noted in
@@ -79,7 +79,7 @@ Vulnerability severity is evaluated on a case-by-case basis, guided by [CVSS
7979
8080We aim to reduce the number of security issues through several general
8181security-conscious development practices including the use of unit-tests,
82- end-to-end (e2e) tests, static and dynamic analysis tools, and use of
82+ end-to-end (e2e) tests, static, and dynamic analysis tools, and use of
8383memory-safe languages.
8484
8585We aim to fix issues discovered by analysis tools as quickly as possible. We
0 commit comments