-
Notifications
You must be signed in to change notification settings - Fork 91
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
Add LAYERS data to XLSX output #1490
Comments
Signed-off-by: tdruez <[email protected]>
The layers data is extracted during the docker analysis pipeline and it is stored in the project This value, when available, is presented in the UI and included as the LAYERS sheet in the XLSX output. The export of the LAYERS sheet was implemented in #735 and only contains a subset of the whole The issue here is that the As anticipated in #735 (comment)
XLSX is not the ideal format to export and load project data. This is especially true for the LAYERS sheet. We can add bit of code to load the available
The codebase data panel presents the data available on disk, it is not available when loading data from an SBOM (or XLSX). |
Signed-off-by: tdruez <[email protected]>
Added in #1491 |
I have run several tests with v34.9.3 using new projects to Clarifying that we loaded the JSON data into SCIO - not XLSX, so the data is available for SCIO to collect during the load_inventory pipeline. |
The See #926 (comment) for the previous discussion on this topic. I've revisited this and implemented a solution, see #926 (comment) The |
For Docker image Scans we always need the LAYERS data. Currently the SCIO XLSX output includes the LAYERS sheet when the image is directly scanned on SCIO, but the XLSX output does not include LAYERS when we download XLSX output for a Docker image Scan with uploaded to SCIO with the
load_inventory
pipeline.I also do not see the Codebase data in the UI for the Scans uploaded with the
load_inventory
pipeline.The key enhancement is to get the LAYERS data in the XLSX output but it would be nice to also be able to see the Codebase data in the UI if possible.
The text was updated successfully, but these errors were encountered: