ci(super-linter): stop Trivy from calling Maven Central - #526
Merged
Conversation
Maven Central answers "429 Too Many Requests" to Trivy's user agent from any IP, and Trivy 0.71.1 (shipped with super-linter v8.7.0) resolves parent and BOM POMs even when its vulnerability scanner is disabled, so every run aborted with a fatal error. Set TRIVY_OFFLINE_SCAN to stop Trivy issuing those requests, and restore the Maven workflow's dependency cache into the home directory that the super-linter container sees, so Trivy still resolves the full dependency tree from disk on the runs that scan for vulnerabilities. A cache miss now costs coverage (a warning) instead of failing the run.
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
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.
Readiness checklist
Please check the boxes below to confirm that you have followed the
required guidelines for contributions:
Fixes #ISSUE_NUMBER.orCloses #ISSUE_NUMBER..Description
Maven Central answers "429 Too Many Requests" to Trivy's user agent from any IP, and Trivy 0.71.1 (shipped with super-linter v8.7.0) resolves parent and BOM POMs even when its vulnerability scanner is disabled, so every run aborted with a fatal error.
Set TRIVY_OFFLINE_SCAN to stop Trivy issuing those requests, and restore the Maven workflow's dependency cache into the home directory that the super-linter container sees, so Trivy still resolves the full dependency tree from disk on the runs that scan for vulnerabilities. A cache miss now costs coverage (a warning) instead of failing the run.