-
Notifications
You must be signed in to change notification settings - Fork 18
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
License information missing from BOM #262
Comments
I believe that would be a problem with syft not the buildpacks. Buildpacks generate their own SBOM information. You don't need to run Can you please try this?
The resulting folder should contain the SBOM information generated by buildpacks for the contents of your application image. We also generate a separate SBOM for the build image, because sometimes more stuff is installed into the build environment. If you want that, you can only fetch it when running Hope that helps! |
Thanks for the help. I ran the
|
Oh, interesting. That is not expected. It should have added the license information from the dependency in buildpack.toml. Switching this to a bug. |
Notes:
|
When generating an sBOM report using Syft for a container image built with the new-relic buildpack, the "New Relic Java Agent" element does not correctly set license information so the Syft tool can export it correctly in an sBOM file.
Expected Behavior
We expect the sBOM file generated by Syft on an image has the
licenseConcluded
andlicenseDeclared
elements of the "New Relic Java Agent" element in the "packages" array set correctly.Current Behavior
Using Syft on an image generated with Paketo with new-relic buildpack included, the "New Relic Java Agent" has incorrect (LicenseRef-) value for the
licenseConcluded
andlicenseDeclared
elements.Possible Solution
Steps to Reproduce
syft <image>
Motivations
The text was updated successfully, but these errors were encountered: