Closed joycebrum closed 11 months ago
Hi,
I'm writing to follow up on your review in this pull request. I noticed that you haven't left any feedback yet.
I'm happy to answer any questions you have about my changes. I'm also available to chat if you'd like to discuss my suggestions in more detail.
If you have any concerns about my changes, please let me know so that I can address them.
I just wanted to let you know that if the PR doesn't have any activity for the next two months, I'll close it. However, if you'd like to keep it open as "not planned," just let me know and I'll be happy to do that.
Thanks!
Our code of conduct strictly prohibits the submission, implementation and suggestion of security policies. Closed.
Closes #416
I've created the SECURITY.md file considering the report vulnerability through security advisory, which is a new github feature still in beta and that has to be enabled.
If you're interested in GitHub's feature, it must be activated for the repository:
If you rather not enable it there is also the possibility to receive the vulnerability report through an email, in this case just let me know which email it would be and I'll submit the change.
Besides that, 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.