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

Create a security policy #15

Open
1 task
StephenCathcart opened this issue Aug 25, 2020 · 0 comments
Open
1 task

Create a security policy #15

StephenCathcart opened this issue Aug 25, 2020 · 0 comments
Assignees
@StephenCathcart
Labels
p:low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix t:documentation Improvements or additions to documentation
Milestone
MVP

Comments

@StephenCathcart
Copy link
Member

Description 🤔

A security policy document needs to be created to help the community understand how to securely report security vulnerabilities for the project. A security template should be created. This template is what users should fill in to report any security issue.

https://github.com/the-pragmatic-dev/meco-api/security/policy

Acceptance Criteria 🎉

  • Written doc blocks, inline documentation or READMEs

Please read CONTRIBUTING.md for details on our code of conduct.
@StephenCathcart StephenCathcart added t:documentation Improvements or additions to documentation p:low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix labels Aug 25, 2020
@StephenCathcart StephenCathcart added this to the MVP milestone Aug 25, 2020
@StephenCathcart StephenCathcart self-assigned this Aug 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@StephenCathcart StephenCathcart

Labels
p:low This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix t:documentation Improvements or additions to documentation
Projects
None yet
Milestone
MVP
Development

No branches or pull requests
1 participant
@StephenCathcart