-
Notifications
You must be signed in to change notification settings - Fork 70
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
Buildpack support for sBOM #269
Buildpack support for sBOM #269
Conversation
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Co-authored-by: Javier Romero <[email protected]>
Co-authored-by: Javier Romero <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally lgtm. Some minor comments.
1. Write a partial Bill-of-Material to `<layers>/build.toml` describing any provided build dependencies. | ||
1. Write a partial Software Bill of Materials to `<layers>/<layer>.sbom.<ext>` describing any dependencies provided in the layer. | ||
1. Write a partial Software Bill of Materials to `<layers>/launch.sbom.<ext>` describing any provided application dependencies not associated with a layer. | ||
1. Write a partial Software Bill of Materials to `<layers>/build.sbom.<ext>` describing any provided build dependencies not associated with a layer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think one thing that I know people have gotten confused about, is where they should write sbom for libraries that were included in an output compiled binary. For eg go libraries in a go binary. Those should technically be in the launch sbom as they are present in the final app image. On the other hand tools like a package manager might be better off in the build sbom. Not sure if we should clarify here or in the docs.
Signed-off-by: Natalie Arellano <[email protected]> Co-authored-by: Sambhav Kothari <[email protected]>
Signed-off-by: Natalie Arellano [email protected]