Fixes #1: Implement Caching and Fallback Mechanism for Trivy Database Fetches#6
Merged
JasonPierce merged 8 commits intomainfrom Apr 3, 2026
Merged
Fixes #1: Implement Caching and Fallback Mechanism for Trivy Database Fetches#6JasonPierce merged 8 commits intomainfrom
JasonPierce merged 8 commits intomainfrom
Conversation
When rate limits or network issues prevent downloading the vulnerability DB, the action now falls back to a cached copy of the database, ensuring continuous operation of security scans
Pass cache_db input through env instead of inline expression to prevent code injection. Extract trivy scan into a reusable function to eliminate command duplication between primary and fallback paths. Widen cache from ~/.cache/trivy/db to ~/.cache/trivy to include Java DB. Add cached DB date to the fallback warning message. Addresses #1
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.
When rate limits or network issues prevent downloading the vulnerability DB, the action now falls back to a cached copy of the database, ensuring continuous operation of security scans