-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip vulnerability reports that are marked as "withdrawn" #385
Comments
This applies immediately to the OSV service backend, but may also apply to PyPI's vulnerability DB (which serves a functional subset of the OSV schema). I'll need to check what PyPI's updated does when a entry is marked as withdrawn. |
(I identified this as part of looking into pytest-dev/py#287 -- we "correctly" report this spam vulnerability at the moment because it isn't marked as withdrawn yet, but we should skip it if/when it's correctly withdrawn.) |
#386 looks good to me but I think we should probably extend support for this to PyPI as well -- shall we create a separate issue for tracking that? |
Yeah, I think so -- I can create that in a moment. |
#388 is the continuation of this, for PyPI's vulnerability service. |
The OSV format supports the
withdrawn
field, which indicates that a report has been withdrawn and is no longer valid.pip-audit
should respect that field and ignore any reports that contain it, so long as the field's timestamp is not after the current time.The text was updated successfully, but these errors were encountered: