Skip to content

Add support for granular lifecycles #277

Open

Description

@prabhu

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

  1. added this to the 1.6 milestone on Aug 14, 2023
  2. stevespringett commented on Feb 5, 2024

    @stevespringett
    Member

    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.

  3. modified the milestones: 1.6, 1.7 on Feb 5, 2024
  4. prabhu commented on Feb 6, 2024

    @prabhu
    ContributorAuthor

    Thanks @stevespringett. I am unable to find time, so moving to 1.7 would help.

  5. modified the milestones: 1.7, 2.0 on Aug 14, 2025
  6. stevespringett commented on Jan 3, 2026

    @stevespringett
    Member

    Ping. Are you able to assist with this ticket for v2.0?

  7. modified the milestones: 2.0, 2.1 on Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions