You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,6 @@ By default, only the latest version of the library is supported. Security patche
9
9
* Suspected security vulnerabilities should not be discussed publicly. Do not open an issue using the normal issue tracker.
10
10
* Create your own fork of this project
11
11
* Create a [Security Advisory](https://docs.github.com/en/code-security/security-advisories/creating-a-security-advisory) in your fork. Do not worry about getting all the settings correct initially.
12
-
*[Grant access](https://docs.github.com/en/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory) to the my username (pjfanning) so that I can see the description of the issue and comment.
12
+
*[Grant access](https://docs.github.com/en/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory) to my username (pjfanning) so that I can see the description of the issue and comment.
13
13
* If I accept that there is a vulnerability, I move the Security Advisory to this project and add all the parties from the fork advisory as collaborators.
14
14
* I will try to get a fix, a release and CVE assignment done as quickly as I can.
0 commit comments