Skip to content
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

Publish SBOM for Each Release #69

Closed
jspeed-meyers opened this issue Feb 4, 2023 · 6 comments
Closed

Publish SBOM for Each Release #69

jspeed-meyers opened this issue Feb 4, 2023 · 6 comments
Labels
enhancement New feature or request P1 Medium priority

Comments

@jspeed-meyers
Copy link
Collaborator

Requirements:

  • SPDX SBOM
  • JSON format
  • Stored in the GitHub releases page

cc @anthonyharrison

@jspeed-meyers jspeed-meyers added enhancement New feature or request P1 Medium priority labels Feb 4, 2023
@jspeed-meyers
Copy link
Collaborator Author

@anthonyharrison, is there an example repo where you do this already?

@anthonyharrison
Copy link
Contributor

@jspeed-meyers There is a GitHub action here which publishes an SBOM every week to the github repository. We publish a separate SBOM for each version of Python which is supported because there are different dependency requirements depending on the Python version being used. There may also be different dependencies related to the target architecture and operating system but I don't think this applies for this project.

@jspeed-meyers
Copy link
Collaborator Author

Thank you, @anthonyharrison. That's useful.

One of the "requirements" (air quotes, because I am making this up as I go along) I created for this task is to publish the created SBOM to the GitHub releases page. IIUC, the Action in the project you highlighted publishes into the project repository. Both are sensible, but my preference is to only create SBOMs for releases.

One of Anchore's actions for syft appears to do this: https://github.com/anchore/sbom-action

I was thinking of trying that action out instead of that approach since the Anchore action default behavior is to release an SBOM to the GH Action release page, though I would prefer to use the sbom4python tool since you are the creator of it and so can help troublesboot. Any objections or thoughts?

@anthonyharrison
Copy link
Contributor

@jspeed-meyers I am not very good with GH actions. But I think if you modify the on action to be on the prelease event rather than on a schedule and find a way to copy the SBOMs to a release (I still think it is worth storing in the repo BTW), then I think you will be there.

@jspeed-meyers
Copy link
Collaborator Author

This might simplify this task: https://github.com/marketplace/actions/sbom-generator-action

@jspeed-meyers jspeed-meyers self-assigned this Apr 19, 2023
@jspeed-meyers jspeed-meyers removed their assignment Nov 25, 2023
@jspeed-meyers
Copy link
Collaborator Author

I am going to close this issue because (A) I don't see evidence that an SBOM associated with the release would benefit anyone and (B) I don't know a simple and reliable way to generate this SBOM. Reader, please re-open this issue if such an SBOM would benefit you or if you know of a simple and reliable way to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P1 Medium priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants