Skip to content

ci: [SC-66825] run zizmor and fix GitHub Actions findings - #77

Merged
mbabic merged 1 commit into
masterfrom
ci/sc-66825/zizmor-ci-and-actions-hardening
Aug 18, 2026
Merged

ci: [SC-66825] run zizmor and fix GitHub Actions findings#77
mbabic merged 1 commit into
masterfrom
ci/sc-66825/zizmor-ci-and-actions-hardening

Conversation

@mbabic

@mbabic mbabic commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Runs zizmor in CI and fixes the findings it reports. Part of sc-66825; modeled on narrative-skills-marketplace PR #108, the reference implementation for this ticket.

Findings fixed

Finding Severity Where Fix
unpinned-uses ×2 High vendored ci.yml removed the dead vendored workflow
excessive-permissions Medium vendored ci.yml as above
artipacked Medium vendored ci.yml as above
excessive-permissions Medium backup-daily.yml permissions: contents: read
secrets-inherit Medium backup-daily.yml dropped secrets: inherit

No suppressions added. Both highs are genuinely fixed, per the ticket's requirement that highs not be muted.

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

Adds a zizmor CI workflow modeled on narrative-skills-marketplace
(PR #108) and fixes the findings it reports.

backup-daily.yml:
- secrets-inherit: drops 'secrets: inherit'. The called workflow only
  uses GITHUB_TOKEN, which is passed to called workflows automatically;
  AWS access comes from the self-hosted runner's instance profile.
- excessive-permissions: scopes the workflow to contents: read.

library/src/plugins/vue-fontawesome/.github/workflows/ci.yml (removed):
All four findings in the vendored tree, including both high-severity
ones (unpinned-uses on actions/checkout@v1 and actions/setup-node@v1),
came from this single file: a vendored copy of FortAwesome's upstream
CI config, untouched since 2020. GitHub only executes workflows under
the repository root's .github/workflows/, so it never ran.

The vendored library source beside it is untouched and still imported
by library/src/index.js, as are the upstream issue templates, which
carried no findings.

No suppressions added.
@mbabic
mbabic force-pushed the ci/sc-66825/zizmor-ci-and-actions-hardening branch from a66e778 to c9b513c Compare August 18, 2026 20:45

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deleted as it was scanned by zizmor and trigger issues. Arguably should remove entire .github dir here, but wanted to keep scope as small as possible.

@mbabic
mbabic merged commit d5923fd into master Aug 18, 2026
2 checks passed
@mbabic
mbabic deleted the ci/sc-66825/zizmor-ci-and-actions-hardening branch August 18, 2026 20:48
@mbabic
mbabic restored the ci/sc-66825/zizmor-ci-and-actions-hardening branch August 18, 2026 21:00
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