I've created the SECURITY.md file following a GitHub's template and considering the report vulnerability through security advisory, which is a handy new GitHub feature, but it's still in beta and has to be manually enabled by a maintainer.
If you're interested in this feature, you can activate it following this steps:
Click on this link to go to Code security & analysis section on your repo's settings
Click "Enable" for "Private vulnerability reporting (Beta)"
However, if you'd rather not use this feature, you can also request users to report vulnerabilities to an email. If that's the case, let me know which email you would like to receive the reports and I can submit the change.
Additionally, feel free to edit or suggest any changes to this document, it is supposed to reflect the amount of effort the team can offer to handle vulnerabilities.
Closes #383
I've created the SECURITY.md file following a GitHub's template and considering the report vulnerability through security advisory, which is a handy new GitHub feature, but it's still in beta and has to be manually enabled by a maintainer.
If you're interested in this feature, you can activate it following this steps:
However, if you'd rather not use this feature, you can also request users to report vulnerabilities to an email. If that's the case, let me know which email you would like to receive the reports and I can submit the change.
Additionally, feel free to edit or suggest any changes to this document, it is supposed to reflect the amount of effort the team can offer to handle vulnerabilities.