Skip to content

[StepSecurity] Apply security best practices #89

[StepSecurity] Apply security best practices

[StepSecurity] Apply security best practices #89

Workflow file for this run

name: Snyk scan
on:
push:
branches:
- main
pull_request:
branches:
- main
jobs:
snyk-security:
permissions:
security-events: write
runs-on: ubuntu-latest
steps:
- name: Harden the runner (Audit all outbound calls)
uses: step-security/harden-runner@df199fb7be9f65074067a9eb93f12bb4c5547cf2 # v2.13.3
with:
egress-policy: audit
- name: Checkout
uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
- name: Run Snyk to check for vulnerabilities
uses: snyk/actions/maven@9adf32b1121593767fc3c057af55b55db032dc04 # master
continue-on-error: true # To make sure that SARIF upload gets called
env:
SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}
with:
args: --all-projects --sarif-file-output=snyk.sarif
- name: Check output file
id: out-file
run: |
if test -f "snyk.sarif"; then
echo "::set-output name=exists::true"; else
echo "::set-output name=exists::false"
fi
- name: Handle undefined security-severity
if: steps.out-file.outputs.exists == 'true'
run: |
sed -i 's/"security-severity": "undefined"/"security-severity": "0"/g' snyk.sarif
- name: Upload result to GitHub Code Scanning
if: steps.out-file.outputs.exists == 'true'
uses: github/codeql-action/upload-sarif@497990dfed22177a82ba1bbab381bc8f6d27058f # v3.31.6
with:
sarif_file: snyk.sarif