The number of ignored matches was not being updated in the TUI, causing confusing numbers to be displayed. For example, scanning the golang:latest resulted in:
Additionally, when using --by-cve, ignored matches were not being reported properly due to applying the ignore rules twice. This PR also corrects that issue, which results in correct counts being reported in the TUI when using that option and correct ignored matches being reported in the JSON. Before:
The number of ignored matches was not being updated in the TUI, causing confusing numbers to be displayed. For example, scanning the
golang:latest
resulted in:With this fix, it now reads:
Additionally, when using
--by-cve
, ignored matches were not being reported properly due to applying the ignore rules twice. This PR also corrects that issue, which results in correct counts being reported in the TUI when using that option and correct ignored matches being reported in the JSON. Before:After:
TODO: