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.

Sign up for GitHub

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

Jump to bottom

Publish a security policy #112

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

Publish a security policy #112

wants to merge 6 commits into 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
Publish a Security Policy #108
Open
2 tasks
tkuhrt
tkuhrt reviewed Feb 9, 2024
View reviewed changes
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
@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
Reviewers

@tkuhrt tkuhrt Awaiting requested review from tkuhrt tkuhrt is a code owner

@rolsonquadras rolsonquadras Awaiting requested review from rolsonquadras rolsonquadras will be requested when the pull request is marked ready for review rolsonquadras is a code owner

@wenjing wenjing Awaiting requested review from wenjing wenjing will be requested when the pull request is marked ready for review wenjing is a code owner

@petecool petecool Awaiting requested review from petecool petecool will be requested when the pull request is marked ready for review petecool is a code owner

@davidz25 davidz25 Awaiting requested review from davidz25 davidz25 will be requested when the pull request is marked ready for review davidz25 is a code owner

@aceshim aceshim Awaiting requested review from aceshim aceshim will be requested when the pull request is marked ready for review aceshim is a code owner

@swcurran swcurran Awaiting requested review from swcurran swcurran will be requested when the pull request is marked ready for review swcurran is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Publish a Security Policy
2 participants
@skounis @tkuhrt