Check Docker images for vulnerabilities and improve image generation #962
Conversation
This file contains 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
gabmontes
requested review from
alvarengathomas,
rafappelt,
dhidalgX and
ArturDolzan
alvarengathomas
approved these changes
Mar 5, 2025
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.
Description
The Docker images are now generated with proper provenance and SBoM in addition to both "ref" and short commit SHA tags.
Vulnerabilities are checked too, using
aquasecurity/trivy-action, which is the same tool DockerHub uses internally. Some NPM cache files were skipped to speed up the scanning process by not checking unneeded files.One vulnerability related to
cross-spawnwas detected in the NPM version that comes globally installed with the Node base image and it was resolved by updating it to a newer version.