You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I scanned a project and found 859 packages, like the following:
But the table below shows that there are only about 630.
This is often confusing.
I found that the package is deduplicated before printing to the table.
There is a similar issue against grype, and the suggestion made there is to mark the rows where there are duplicates with the number of instances found. Why not go the other way around (report the de-duplicated number in the TUI output)? Because in other output formats, such as the JSON output, the de-duplicated count is what will be used.
wagoodman
changed the title
Confusing number of packages
TUI package count does not reflect count in default table output
Feb 29, 2024
wagoodman
changed the title
TUI package count does not reflect count in default table output
TUI package count does not match package count in default table output
Feb 29, 2024
What happened:
I scanned a project and found 859 packages, like the following:
But the table below shows that there are only about 630.
This is often confusing.
I found that the package is deduplicated before printing to the table.
syft/syft/format/table/encoder.go
Line 64 in 928511e
What you expected to happen:
Should there be an obvious hint?
Steps to reproduce the issue:
Anything else we need to know?:
Environment:
syft version
: mastercat /etc/os-release
or similar): macThe text was updated successfully, but these errors were encountered: