You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure I understand the question. Do you want to include the Python version used for runtime or compiling in the bom as another component?
If so, there isn't a direct way to do this, however, the CycloneDX spec was intentionally designed to be simplistic to account for the dynamic addition of runtime and environmental dependencies not part of the build itself. In this case, you could simply create an XML fragment with the Python component information and use one of the many XML CLI utilities to append the fragment in the components node.
The Node version does something similar where it can optionally merge multiple boms together.
Activity
stevespringett commentedon Feb 19, 2020
Not sure I understand the question. Do you want to include the Python version used for runtime or compiling in the bom as another component?
If so, there isn't a direct way to do this, however, the CycloneDX spec was intentionally designed to be simplistic to account for the dynamic addition of runtime and environmental dependencies not part of the build itself. In this case, you could simply create an XML fragment with the Python component information and use one of the many XML CLI utilities to append the fragment in the components node.
The Node version does something similar where it can optionally merge multiple boms together.
coderpatros commentedon Sep 3, 2020
Closing this due to inactivity.
KramNamez commentedon Jul 25, 2022
Can I ask why there's no direct way to include the runtime Python version in the SBOM?
I would have naively thought that it's an important dependency, too.