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
{{ message }}
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.
We can have thousands of vulnerable version ranges for a popular project, which are too slow too lookup against actual versions to determine their vulnerable status. To cope with that, we simplify vulnerable ranges using a simple algorithm:
take largest range which doesn't have left bound (e.g. (-∞, ver))
remove all ranges covered by it
This reduces number of ranges by 20x, but it can be further improved by at least extending the range by closed ranges intersecting it (e.g. (-∞, 1.2] + [1.1, 1.3] = (-∞, 1.3]), or, better, fair merger of all available ranges.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We can have thousands of vulnerable version ranges for a popular project, which are too slow too lookup against actual versions to determine their vulnerable status. To cope with that, we simplify vulnerable ranges using a simple algorithm:
(-∞, ver)
)This reduces number of ranges by 20x, but it can be further improved by at least extending the range by closed ranges intersecting it (e.g.
(-∞, 1.2]
+[1.1, 1.3]
=(-∞, 1.3]
), or, better, fair merger of all available ranges.The text was updated successfully, but these errors were encountered: