-
Notifications
You must be signed in to change notification settings - Fork 165
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
SBOM files for some artifacts are almost empty #488
Comments
@cpanato, do you have an idea on what's going on? @cartersocha, this is the issue we talked about during the SIG Security call. |
hum looks like it is doing working well with the .tar.gz, i think that is better only with the binary, i can change that |
seems we need to pass some config options run locally (with the correct version now)
|
i run the gorelease locally and the sboms was created with data |
we need to make sure we have the latest syft, checking that |
was able to reproduce the issue with |
we need to wait for anchore/sbom-action#456 |
Thank you for the investigation! |
We have SBOMs since v0.95.0, but some artifacts seem to be missing the actual contents of the package, like the one for otelcol-contrib_0.95.0_darwin_amd64.tar.gz.sbom:
Some other entries, like otelcol_0.95.0_windows_amd64.tar.gz.sbom , seem to have an appropriate content, containing things like:
We need to investigate what's the difference, and how we can get the packages to be like the SBOMs for Windows.
The text was updated successfully, but these errors were encountered: