Skip to content

Fixes #1: Implement Caching and Fallback Mechanism for Trivy Database Fetches#6

Merged
JasonPierce merged 8 commits intomainfrom
feature/issue-1
Apr 3, 2026
Merged

Fixes #1: Implement Caching and Fallback Mechanism for Trivy Database Fetches#6
JasonPierce merged 8 commits intomainfrom
feature/issue-1

Conversation

@JasonPierce
Copy link
Copy Markdown
Contributor

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

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
Comment thread run-trivy/action.yml Fixed
Comment thread run-trivy/action.yml Fixed
Comment thread run-trivy/action.yml Fixed
Comment thread run-trivy/action.yml Fixed
Comment thread run-trivy/action.yml Fixed
Comment thread run-trivy/action.yml Fixed
Comment thread run-trivy/action.yml Fixed
Comment thread run-trivy/action.yml Fixed
Comment thread run-trivy/action.yml Fixed
Comment thread run-trivy/action.yml Fixed
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
@JasonPierce JasonPierce merged commit 34c7c42 into main Apr 3, 2026
17 checks passed
@JasonPierce JasonPierce deleted the feature/issue-1 branch April 3, 2026 03:58
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.

2 participants