The current "Detected Licenses" view is license-centric, meaning that findings are grouped by license and then by package. This makes sense to generally identify problematic licenses, but in order to identify problematic packages (due to licensing issues), we should have an additional view where the top-level entity is a package / project.
Instead of re-adding the complex grouping functionality we once had for some tables / columns, the idea is to have either radio buttons or tabs within the existing "Detected Licenses" view where a "by license" table shows the current table, and a "by package / project" table shows a new table that lists packages and projects.
This table should be similar to the existing "Projects" / "Packages" views in that a collapsed row should display the ID and (abbreviated) detected license below, and when expanding, license findings should be show like currently done in the license-centric view.
The current "Detected Licenses" view is license-centric, meaning that findings are grouped by license and then by package. This makes sense to generally identify problematic licenses, but in order to identify problematic packages (due to licensing issues), we should have an additional view where the top-level entity is a package / project.
Instead of re-adding the complex grouping functionality we once had for some tables / columns, the idea is to have either radio buttons or tabs within the existing "Detected Licenses" view where a "by license" table shows the current table, and a "by package / project" table shows a new table that lists packages and projects.
This table should be similar to the existing "Projects" / "Packages" views in that a collapsed row should display the ID and (abbreviated) detected license below, and when expanding, license findings should be show like currently done in the license-centric view.