Report security vulnerabilities using GitHub#14549
Conversation
Pierre-Sassoulas
left a comment
There was a problem hiding this comment.
👍 Did you also switch the tidelift config ? This can have financial consequences.
Good call, there's probably a setting/link in there that should be updated. Shouldn't affect financials though, it was suggested in a email thread by their own support. |
|
More context: yesterday Tidelift reached out to me about a report, and one of the ways we could move the report forward was to enable the GitHub feature, which seems like a good idea as is easier for users and directly integrated into our workflow. |
|
Previously the change would have happened here: https://tidelift.com/lifter/package/pypi/pytest/tasks/packages_have_security_policies (but it seems there's a new policy) |
Direct users to report security vulnerabilities using GitHub's security advisory. This was one of the options suggested by Tidelift's support during an email exchange about a new vulnerability, which seems like a good idea as is easier for users and directly integrated into our workflow.
e446ac3 to
5136a19
Compare
|
Thanks for the link! We need a |

Direct users to report security vulnerabilities using GitHub's security advisory, which I just enabled in the repository.