feat: Add Trivy security scanning to Docker workflows

- Add Trivy vulnerability scanner after image build
- Upload SARIF results to GitHub Security tab
- Display critical/high severity issues in workflow logs
- Add security-events permission for SARIF upload
- Skip scanning on pull requests to save time
This commit is contained in:
Wikid82
2025-11-18 17:23:13 -05:00
parent c979e3d417
commit 95823204a6
2 changed files with 50 additions and 1 deletions

View File

@@ -23,6 +23,7 @@ jobs:
permissions:
contents: read
packages: write
security-events: write
steps:
- name: Checkout repository
@@ -74,3 +75,26 @@ jobs:
- name: Image digest
run: echo ${{ steps.build-and-push.outputs.digest }}
- name: Run Trivy vulnerability scanner
if: github.event_name != 'pull_request'
uses: aquasecurity/trivy-action@master
with:
image-ref: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}@${{ steps.build-and-push.outputs.digest }}
format: 'sarif'
output: 'trivy-results.sarif'
- name: Upload Trivy results to GitHub Security
if: github.event_name != 'pull_request'
uses: github/codeql-action/upload-sarif@v3
with:
sarif_file: 'trivy-results.sarif'
- name: Run Trivy scan (table output)
if: github.event_name != 'pull_request'
uses: aquasecurity/trivy-action@master
with:
image-ref: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}@${{ steps.build-and-push.outputs.digest }}
format: 'table'
severity: 'CRITICAL,HIGH'