Remove the Safety scanner from the pre-commit hooks and GitHub action #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since February, I have been using the Safety scanner as part of my pre-commit hooks and GitHub actions, to identify vulnerabilities in Python dependencies. Even though Safety is distributed under the liberal MIT license, and the PyPI package page documents that Safety can be used in this manner, the PyUp organization behind Safety now claims that this usage is not allowed. Despite my repeated attempts to clarify what I was doing wrong, PyUp's representative never offered any specifics. I don't think Safety adds enough value to pursue this further, so I'm just removing all usage of Safety. I'll rely on Dependabot instead. I have included some notes, including the bizarre email conversation with PyUp.