Repository navigation
Scan the images for secrets and write a bill of materials - #54
Merged
Merged
Conversation
The scan looked at the vulnerabilities of the packages only. The images are scanned for secrets as well now, a secret in an image fails the build. Every build writes a bill of materials of the image and uploads it, so the components of a published image can be listed later. The dependencies of a pull request are reviewed, a change that brings in a package with a known vulnerability or with a license that is not allowed fails the review. The release workflow scans every platform of the published image, not only the one of the runner. The release of the image is only created when every platform is clean.
The file with the pinned versions is the manifest that the dependency graph of the repository uses, it is the reason the dependencies of a pull request can be reviewed. The pipeline installs the versions of the file now.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The scan looked at the vulnerabilities of the packages only. The images are scanned for secrets as well now, a secret in an image fails the build.
Every build writes a bill of materials of the image and uploads it, so the components of a published image can be listed later.
The dependencies of a pull request are reviewed, a change that brings in a package with a known vulnerability or with a license that is not allowed fails the review.
The release workflow scans every platform of the published image, not only the one of the runner. The release of the image is only created when every platform is clean.