-
Notifications
You must be signed in to change notification settings - Fork 571
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
Surface Rust dependency relationships #2353
Comments
Hi @Dungeon1, thanks for the report. I can confirm that the dependencies show up in the syft-json format output, but not the cyclonedx-json or cyclonedx-xml output. I will confirm with the team if this is expected behavior or not and get back to when we are able to look. Thanks again. |
I'm trying to understand the details. To be clear, this cargo.lock is not sufficient to show all dependencies in the SBOM:
But this would:
Assuming that you have a cargo.lock file that looks like the last example, I think you're really asking why are there not relationships between all of the nodes in your SBOM to show how the nodes are related. If that's true, you're right, we haven't done that work yet. We have another issue to add these for all ecosystems #572 . The nice thing about the rust cataloger is that, for this specific ecosystem, this looks to be low hanging fruit (ready to be implemented around here, correlating the |
@wagoodman I ran on Cargo.lock like your example. |
Cargo.lock had dependencies, but syft not building dependencies with dependsOn. |
I was also able reproduce this. It looks like syft is detecting the dependencies (because they show up in |
What happened:
Syft not created "dependencies" in cyclonedx report for Go, Rust, Java and etc.
Cargo.lock had "dependencies". View like
But output syft doesnt reflect this
What you expected to happen:
Want full cyclonedx report with "dependencies" and "depensOn" included
Steps to reproduce the issue:
syft -o [email protected] Cargo.lock > report.json
Anything else we need to know?:
Environment:
Syft 0.94
The text was updated successfully, but these errors were encountered: