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
Updated SECURITY.MD file with relevant details. (#324)
* Update SECURITY.md
* Update SECURITY.md
I have updated the Security.md file by listing all the versions released yet and the latest version that is being worked on is being supported with security patches.
Steps to report a vulnerablity is same as mentioned in the docs.
* Update SECURITY.md
* Update SECURITY.md
Copy file name to clipboardExpand all lines: SECURITY.md
+10-12Lines changed: 10 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -2,20 +2,18 @@
2
2
3
3
## Supported Versions
4
4
5
-
Use this section to tell people about which versions of your project are
6
-
currently being supported with security updates.
5
+
Only the lastest version are supported with updates.
6
+
7
+
| Version | Supported |
8
+
| ---------- | ------------------ |
9
+
| 20220608.2 |:white_check_mark:|
10
+
7
11
8
-
| Version | Supported |
9
-
| ------- | ------------------ |
10
-
| 5.1.x |:white_check_mark:|
11
-
| 5.0.x |:x:|
12
-
| 4.0.x |:white_check_mark:|
13
-
| < 4.0 |:x:|
14
12
15
13
## Reporting a Vulnerability
16
14
17
-
Use this section to tell people how to report a vulnerability.
15
+
Please report successful attacks with example input via OWASP's bugcrowd queue or contact mikesamuel@gmail.com and I will create a repository security advisory to coordinate.
16
+
17
+
If you wish to be credited, please provide a name or handle for me to credit.
18
18
19
-
Tell them where to go, how often they can expect to get an update on a
20
-
reported vulnerability, what to expect if the vulnerability is accepted or
21
-
declined, etc.
19
+
If you wish to remain anonymous, please create a sock account, and email the address above.
0 commit comments