Skip to content

ci(super-linter): stop Trivy from calling Maven Central - #526

Merged
thomasleplus merged 2 commits into
mainfrom
ci/trivy-maven-cache
Sep 2, 2026
Merged

ci(super-linter): stop Trivy from calling Maven Central#526
thomasleplus merged 2 commits into
mainfrom
ci/trivy-maven-cache

Conversation

@thomasleplus

Copy link
Copy Markdown
Owner

Readiness checklist

Please check the boxes below to confirm that you have followed the
required guidelines for contributions:

  • If this pull request includes code changes, they were all properly tested. Automated tests were also included where possible.
  • If applicable, this pull request includes the relevant documentation for this change.
  • If this pull request is related to an existing issue, you can use the same description below but in any case include a link to the issue like Fixes #ISSUE_NUMBER. or Closes #ISSUE_NUMBER..
  • All the commits in this pull request were squashed into a single commit. That commit is signed.

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.

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.
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
actions/actions/cache/restore 55cc8345863c7cc4c66a329aec7e433d2d1c52a9 🟢 6.4
Details
CheckScoreReason
Maintained🟢 1013 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 10all changesets reviewed
Binary-Artifacts🟢 10no binaries found in the repo
Packaging⚠️ -1packaging workflow not detected
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
Fuzzing⚠️ 0project is not fuzzed
License🟢 10license file detected
Signed-Releases⚠️ -1no releases found
Security-Policy🟢 9security policy file detected
Branch-Protection⚠️ 1branch protection is not maximal on development and all release branches
SAST🟢 10SAST tool is run on all commits

Scanned Files

  • .github/workflows/super-linter.yml

@thomasleplus
thomasleplus merged commit 0939e74 into main Sep 2, 2026
1 check passed
@thomasleplus
thomasleplus deleted the ci/trivy-maven-cache branch September 2, 2026 19:55
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 this pull request may close these issues.

1 participant