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
SBoM generation tools (like cdxgen) might encounter artifacts already built along with source code and package manager manifests. In such cases, indicating the lifecycle phases associated with the given component(s) or their parent component(s) would be nice.
In 1.5, lifecycles can be an array of values or name-description objects. Similar to component evidence, lifecycles could optionally accept bom-link, bom-ref, purl, and cpe to make it granular. In addition, we can also add evidencemethods so that the generator can justify how and why it thinks the components or the bom belong to a particular phase. Understanding the tool's assumptions is useful since the definition of build and post-build differs based on the organization and team.
Activity
stevespringett commentedon Feb 5, 2024
This needs to be flushed out. Can you provide some mockups on what your thoughts are. Moving to v1.7 to give us time to flush this out.
prabhu commentedon Feb 6, 2024
Thanks @stevespringett. I am unable to find time, so moving to 1.7 would help.
stevespringett commentedon Jan 3, 2026
Ping. Are you able to assist with this ticket for v2.0?