-
Notifications
You must be signed in to change notification settings - Fork 232
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
Break number of vulnerabilities further down -> Image/TARGET #2487
Comments
Hi @hpvd Thanks! Let us think a bit where this information could fit nicely. We'd rather not to add more entries to the summary table as it's already quite long in some cases. |
Hi @tegioz fully agree, that a detailed information like this not fits nicely into the main table. |
Closes #2487 Signed-off-by: Cintia Sanchez Garcia <cynthiasg@icloud.com>
Closes #2487 Signed-off-by: Cintia Sanchez Garcia <cynthiasg@icloud.com>
Closes #2487 Signed-off-by: Cintia Sanchez Garcia <cynthiasg@icloud.com>
Closes #2487 Signed-off-by: Cintia Sanchez Garcia <cynthiasg@icloud.com>
This is ready @hpvd 🙂 |
wow looks and works great :-) |
Is your feature request related to a problem? Please describe.
Just working with your great security overview (modal), to identify the priorities to work on within a complete helm chart.
e.g. https://artifacthub.io/packages/helm/apache/pulsar?modal=security-report
For this it would be pretty handy, to have the break-down of the severity of the vulnerabilities further down till the "Target"-layer (it's already down to image-layer, see attachment).
Having this, one would not have to count in each target-layer the number of vulnerabilities for each severity-level.
Describe the solution you'd like
showing the sums of vulnerabilities per severity-level for each target-layer (total and fixable).
This would save the process of manual counting, which may occur several times for each helm chart, since numbers change over time...
Describe alternatives you've considered
manual counting...
Additional context
The text was updated successfully, but these errors were encountered: