CSHARP-6292Needs Triage

Connect all included package dependencies to the root component in the generated SBOM

The SBOM generated by generate-sbom.sh lists every dependency as a component, but some direct dependencies of the in-solution projects (for example AWSSDK.SecurityToken, System.Memory and System.Runtime.CompilerServices.Unsafe) have no dependency path from the root component, so tools that traverse the dependency graph from the root miss them and their subtrees. The cause is that the four driver projects are not components in the SBOM, and their direct dependencies are not attached to the root.

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification
prodsec-program-ssdlc