-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish a security policy #112
base: main
Are you sure you want to change the base?
Publish a security policy #112
Conversation
1584dc8
to
0e913c1
Compare
@tkuhrt This PR establishes the security policy for this repository. However, a step is missing: Compile the security response team and update the table. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we believe that we need a security vulnerability policy for this repository? In general, if there are security vulnerabilities, they will be in the version of Material for Mkdocs that we utilize. All other files that are here are markdown files.
Signed-off-by: Stavros Kounis <skounis@gmail.com>
Signed-off-by: Stavros Kounis <skounis@gmail.com>
Signed-off-by: Stavros Kounis <skounis@gmail.com>
This reverts commit a0b3f1f. Signed-off-by: Stavros Kounis <skounis@gmail.com>
Signed-off-by: Stavros Kounis <skounis@gmail.com>
Signed-off-by: Stavros Kounis <skounis@gmail.com>
2b5da87
to
92dcad1
Compare
I agree, it's prudent to have a security vulnerability policy in place, especially considering that potential vulnerabilities could arise in the version of Material for Mkdocs we're using. Enabling reporting for any security updates we might miss would be beneficial. |
No description provided.