Replies: 1 comment
-
|
This is tracked in #8552 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description
Trivy is moving fast, releasing monthly with new features and fixes being introduced constantly, sometimes the UI/usage of trivy changes. Avid users are following release notes and adapting, but substential portion of users are using old versions and patterns. It would be beneifical to make this information available for users right within the tool, instead of relying on them actively searching for it online as many popular dev tools do (see below).
High level implementation proposal:
Note: This is related but distinct from assets (e.g trivy-db) updating mechanism. As that one is mandatory for normal operation it has different requirements (for example it is blocking, it is taking action).
examples:
Target
None
Scanner
None
Beta Was this translation helpful? Give feedback.
All reactions