You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For each of the available inputs, support adding a --fix flag which will automatically update the dependency specification or environment in question to exclude any found vulnerabilities.
For example:
if a vulnerability is found in a local environment, uninstall it and install a version with the fix
if a vulnerability is found in a requirements.txt file, update the version specification for the affected project to exclude the vulnerable version
This should be a meta-issue for determining the UX around this feature, and we should create sub-issues for each of the potential ways a fix can be applied.
An idle thought around the UX: anything that involves fixes should also support a --dry-run mode, where we tell the user what actions we'd take (e.g. updating a dep in their environment, rewriting their requirements.txt).
I've opened #214 and #215 to track the remainder of this work. I'm going to repurpose this ticket to only capture the work for implementing --fix for PipSource.
tetsuo-cpp
changed the title
Support pip-audit --fix
Implement --fix for PipSourceJan 13, 2022
For each of the available inputs, support adding a
--fix
flag which will automatically update the dependency specification or environment in question to exclude any found vulnerabilities.For example:
requirements.txt
file, update the version specification for the affected project to exclude the vulnerable versionThis should be a meta-issue for determining the UX around this feature, and we should create sub-issues for each of the potential ways a fix can be applied.
--fix
forPipSource
#212--fix
in JSON and columnar formats #215The text was updated successfully, but these errors were encountered: