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
{{ message }}
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.
Do we need a replacement CLI by the time we remove Snyk? - Product call?
Do we keep the existing codebase or start from scratch?
Do we need to do anything to ensure the code can be consumed as a library in desktop instead of being run as an external executable?
What is the CLI named? docker index or docker X or docker image <analyse|report|...> - worth creating an alias as well? Maybe need to extend the plugins system to allow plugins to insert aliases.
What functionality do we need to clean up? - Obtaining an image from a daemon and a registry etc, loading it down, downloading. Local branch for buildkit attestations and shortcut the SBOM generation and use the one from the image, theres a lot of redirection here and hacky code to get it working.
What output format(s) do we want to support? SPDX does not support vulns.. cyclonedx does... do we need to separate (a) SBOM output and (b) Vulnerability reports?
What does a pretty human output look like, colors, tables etc?
Which mechanisms of obtaining SBOMs do we want to support? Can we use buildkit code to generate the SBOM?
Do we want to do anything with docker sbom command?
What params / flags do we need to support? Severity filtering?
Should the codebase be open or closed source?
Next steps:
Yves to look more at the codebase
The text was updated successfully, but these errors were encountered:
Questions:
docker index
ordocker X
ordocker image <analyse|report|...>
- worth creating an alias as well? Maybe need to extend the plugins system to allow plugins to insert aliases.docker sbom
command?Next steps:
The text was updated successfully, but these errors were encountered: