-
Notifications
You must be signed in to change notification settings - Fork 546
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
db status
does not validate vulnerability.db
#1975
Comments
To further clarify this, as this issue might seem a little bit constructed. I was trying to run So i decided to use This worked, until it didn't. I suspect some network hiccup that lead to an invalid database directory without When
Trying to have an early stop to my CI/CD pipeline. I tried using While trying to provoke an invalid database, I came across this issue. |
note: this is a duplicate of #1648 |
What happened:
grype db status
does not validatevulnerability.db
hash.What you expected to happen:
grype db status
fully validates thevulnerability.db
and fails on an invalid db.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Scans with
grype
, do not report a invalid DB either:Environment:
The text was updated successfully, but these errors were encountered: