Vulnerability database version isn't outputted by default during scanning operations #6264
chrisnovakovic
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
|
Hello @chrisnovakovic @knqyf263 what do you think about moving info about trivy-db from |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
|
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
Trivy only outputs the version of the database used in a scan when the
--debugoption is given. Compare:with:
It's useful to know which version of the database is being used in a scan, especially if Trivy is run as part of an automated process whose logs are collected and saved (e.g. a GitHub action), because the database version and the results Trivy provides are intrinsically connected. However, it feels excessive to have to opt in to everything else at the
DEBUGlog level to get this information. (It's also worth noting that the Java DB download messages are logged atINFOlevel, and are therefore outputted by default.)Desired Behavior
By default, Trivy logs the version of the database that was used to perform scanning operations. Something like:
Actual Behavior
It is necessary to specify
--debugwhen running Trivy to display the version of the database that was used to perform scanning operations, although this also produces many other messages that aren't useful most of the time.Reproduction Steps
Target
Container Image
Scanner
Vulnerability
Output Format
Table
Mode
Standalone
Debug Output
Operating System
Ubuntu 22.04
Version
Checklist
trivy image --resetBeta Was this translation helpful? Give feedback.
All reactions