-
Notifications
You must be signed in to change notification settings - Fork 32
Enhancement: Use SBOM generated by Cargo #192
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
Comments
I think the Cargo SBOM is produced after compiling a crate, while cargo-auditable needs to know it before compiling the crate to be able to inject an object file with the sbom when linking. |
Yes, this is absolutely on my radar, both for I am currently seeking funding to be able to work full-time on |
Regarding the time when the SBOM is written: I specifically called out in the RFC for this functionality that the SBOM has to be written before the crate is actually compiled to be usable to Here's a quick Linux-only test to prove that the native SBOM is usable for cargo-auditable: Name this #!/bin/sh
env > "$HOME"/env.dump
cp "$CARGO_SBOM_PATH" "$HOME"
"$@" And run this on your Cargo project: If it all worked, you will see The script ignores multi-target crates for simplicity, so best run this on a "hello world". |
Will ask around if funding is available for such a project from our company.
Good to know! Will try and see if that works |
That might not be needed, if we're lucky. I've already found an entity that is quite enthusiastic about funding this work. We'll see if it converts into actual funding. Once it's clear if this works out or falls through, I'll let you know. |
Please let me know if there are issues using Cargo's SBOM support in Having more projects (especially OSS projects) using the feature gets us closer to stabilization in Cargo. |
Hello,
With the merge of the Cargo SBOM into Cargo Nightly (rust-lang/cargo@7ea222d), it would be a valuable addition to the
cargo-auditable
code to ingest the dependencies from the generated SBOM.It would probably solve a lot of common issues related to
cargo metadata
command.I think
cargo-auditable
is still very relevant in generating the SBOMs from tools likesyft
when using containers that have their own dependencies and would love to see this work incargo-auditable
.let me know if there is anything I could do to help this effort, if you need help with contributions especially.
The text was updated successfully, but these errors were encountered: