Skip to content
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

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

skounis
Copy link
Contributor

@skounis skounis commented Feb 9, 2024

No description provided.

@skounis skounis force-pushed the feat/issue-108-securitypolicy branch from 1584dc8 to 0e913c1 Compare February 9, 2024 09:02
@skounis
Copy link
Contributor Author

skounis commented Feb 9, 2024

@tkuhrt This PR establishes the security policy for this repository. However, a step is missing: Compile the security response team and update the table.

@skounis skounis linked an issue Feb 9, 2024 that may be closed by this pull request
2 tasks
Copy link
Collaborator

@tkuhrt tkuhrt left a 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.

SECURITY.md Outdated Show resolved Hide resolved
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>
@skounis skounis force-pushed the feat/issue-108-securitypolicy branch from 2b5da87 to 92dcad1 Compare February 9, 2024 18:31
@skounis
Copy link
Contributor Author

skounis commented Feb 9, 2024

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.

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.

@tkuhrt tkuhrt self-requested a review February 9, 2024 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Publish a Security Policy
2 participants