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

Auto-attach Grype report as release asset #47

Closed
Tracked by #15
RothAndrew opened this issue Jun 30, 2023 · 0 comments · Fixed by #44
Closed
Tracked by #15

Auto-attach Grype report as release asset #47

RothAndrew opened this issue Jun 30, 2023 · 0 comments · Fixed by #44
Assignees

Comments

@RothAndrew
Copy link
Member

RothAndrew commented Jun 30, 2023

As a user of this image I want to be aware of what vulnerabilities it has, so that I have all the info I need when deciding whether I am able to use it in any particular environment.

As a developer of this image I want to be aware of the changes in vulnerabilities as I make my changes, so that I can ensure that I am not adding new unknown vulnerabilities.

AC:

  • Whenever a new release is created, after the image has been built and pushed, a Grype report of the Syft SBOM is automatically attached to the release as a release artifact
@RothAndrew RothAndrew changed the title Whenever a new release is created, after the image has been built and pushed, a Grype report of the Syft SBOM is automatically attached to the release as a release artifact Auto-attach Grype report as release asset Jun 30, 2023
@RothAndrew RothAndrew self-assigned this Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant