I maintain depquiet . It sits on top of pip-audit, uv audit and npm audit and tries to cut down the noise. The one rule I care about is that it should never hide something real.
This week I found out how close I came to breaking it with what looked like a simple bug fix.
The setup
depquiet had an EPSS filter. EPSS is a score from FIRST.org that estimates how likely a CVE is to get exploited in the next 30 days. My defaults were:
under 10%: filter it out
under 30%: move it to "review"
I picked those numbers because they felt sensible. Most CVEs never get exploited, so why bug people about them?
Then I noticed the filter basically never ran on Python projects. EPSS only works with CVE ids, and pip-audit gives you ids like PYSEC-2023-74 . uv audit gives you GHSA-... . The CVE is there, but as an alias, and depquiet wasn't looking at aliases. No CVE, no score, no filtering.
Easy fix, right?…