Skip to content

Commit 62bbec5

Browse files
committed
SECURITY.md: split out security-relevant bits from readme
GitHub has recently introduced a new set of tools that aims to ease the process around vulnerability reports and security fixes. Part of those tools is a new security tab for projects that will display contents from a new SECURITY.md file. Move relevant parts from README.md to this new file to make use of this feature.
1 parent 7a0238b commit 62bbec5

File tree

2 files changed

+15
-3
lines changed

2 files changed

+15
-3
lines changed

README.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -103,9 +103,7 @@ We ask that you not open a GitHub Issue for help, only for bug reports.
103103

104104
**Reporting Security Issues**
105105

106-
In case you think to have found a security issue with libgit2, please do not
107-
open a public issue. Instead, you can report the issue to the private mailing
108-
list [security@libgit2.com](mailto:security@libgit2.com).
106+
Please have a look at SECURITY.md.
109107

110108
What It Can Do
111109
==============

SECURITY.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
This project will always provide security fixes for the latest two released
6+
versions. E.g. if the latest version is v0.28.x, then we will provide security
7+
fixes for both v0.28.x and v0.27.y, but no later versions.
8+
9+
## Reporting a Vulnerability
10+
11+
In case you think to have found a security issue with libgit2, please do not
12+
open a public issue. Instead, you can report the issue to the private mailing
13+
list [security@libgit2.com](mailto:security@libgit2.com). We will acknowledge
14+
receipt of your message in at most three days and try to clarify further steps.

0 commit comments

Comments
 (0)