Skip to content

Commit 61ddf32

Browse files
committed
SECURITY POLICY BETTER
1 parent 76c1ff1 commit 61ddf32

1 file changed

Lines changed: 15 additions & 2 deletions

File tree

SECURITY.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,22 @@ As of the 2.0.0 re-factor only versions ≥ 2.0.0 will receive support. Versions
1515

1616
This list will be updated when future releases are made in the 2-version series that require specific callouts for supportability.
1717

18-
## Reporting a Vulnerability
18+
If you have discovered what you think is a harmful bug with the potential for exploitation in a supported version series, and this bug may lead to loss of life or data, then you have two options for reporting available to you:
1919

20-
If you have discovered what you think is a harmful bug with the potential for exploitation that will lead to loss of life or data, then reach out to the maintainer at this email address:
20+
## [1] Self-Reporting (GitHub)
21+
22+
Consider using the new [Private Vulnerability Reporting](https://docs.github.com/en/code-security/how-tos/report-and-fix-vulnerabilities/privately-reporting-a-security-vulnerability) function if you want to get involved that way.
23+
24+
* On GitHub, navigate to the main page of the repository.
25+
* Under the repository name, click the Security and quality tab. If you cannot see the " Security and quality" tab, select the dropdown menu, and then click Security and quality.
26+
* Click Report a vulnerability to open the advisory form.
27+
* Fill in the advisory details form.
28+
29+
...as described in the linked GitHub documentation.
30+
31+
## [2] Reporting a Vulnerability (Non-GitHub)
32+
33+
You may also reach out to me at this email address:
2134

2235
* `bitmath@lnx.cx`
2336

0 commit comments

Comments
 (0)