Zoltan KochanandClaude Opus 5.5
902b4a8efd
zizmor 1.31.0 stopped applying ignore comments to the dangerous-triggers audit, so the three workflow_run workflows failed the zizmor check on every fork pull request. zizmor-action v0.7.1 defaults to zizmor 1.31.1, which fixes the regression. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
40 lines
1.2 KiB
YAML
40 lines
1.2 KiB
YAML
name: GitHub Actions Security Analysis with zizmor
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- main
|
|
- 'release/**'
|
|
pull_request:
|
|
branches:
|
|
- main
|
|
- 'release/**'
|
|
|
|
permissions: {}
|
|
|
|
concurrency:
|
|
group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.event.pull_request.number || github.run_id }}
|
|
cancel-in-progress: ${{ github.event_name == 'pull_request' }}
|
|
|
|
jobs:
|
|
zizmor:
|
|
name: zizmor latest via PyPI
|
|
runs-on: blacksmith-4vcpu-ubuntu-2404
|
|
permissions:
|
|
security-events: write
|
|
contents: read
|
|
actions: read
|
|
steps:
|
|
- name: Checkout repository
|
|
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
|
|
with:
|
|
persist-credentials: false
|
|
|
|
- name: Run zizmor
|
|
uses: zizmorcore/zizmor-action@85b2b9fb8e3325e7a23d7d0a9d7ba5ae0f999e3e # v0.7.1
|
|
with:
|
|
# Fork PRs run with a read-only GITHUB_TOKEN, so SARIF upload to
|
|
# Code scanning would fail. In that case, run zizmor anyway and
|
|
# print findings to the console instead.
|
|
advanced-security: ${{ github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository }}
|