Improving pipenv check command with the new Safety options #5355
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.
The issue
Safety >= changed its JSON output leading to a strange output by the pipenv check command.
The fix
Safety >= 2.0 includes new options and improvements; this PR includes the new options and renders the improved Safety screen output, which offers more information to the users about the scan done.
This pull request is related to #5218
The checklist
module 'ruamel.yaml' has no attribute 'resolver'