Skip to content

ci: add zizmor config for audits that don't apply here - #955

Merged
andykenward merged 1 commit into
mainfrom
chore/code-scanning-triage
Oct 20, 2026
Merged

andykenward merged 1 commit into
mainfrom
chore/code-scanning-triage

Conversation

@andykenward

Copy link
Copy Markdown
Owner

Summary

Adds .github/zizmor.yml so the 12 open zizmor code-scanning alerts stop being reported, with the reason for each next to the rule:

  • self-repository (11 notes, one per uses: ./...): GitHub's uses: $/path syntax (2026-07-30, runner 2.336.0+) is rejected by act (uses: $/... self-repository references are rejected nektos/act#6189, open), which pnpm run act:d depends on. Disabled until act supports it.
  • dangerous-triggers on release.yml's workflow_run: the job checks out main at its own ref, never pull request code, and pushes with an app token, so the hazard the audit targets does not apply. Ignored for that one line.

Also notes the config in .claude/rules/workflows.md.

The six open CodeQL alerts are false positives in the same shape as ones dismissed on 2026-09-11 and are being dismissed in the UI, not fixed in code.

Validation

Ran zizmor 1.30.1 in Docker against .github/ with this config: no findings (1 ignored, 41 suppressed). CI's zizmor job covers the same on this PR.

🤖 Generated with Claude Code

The self-repository audit wants `uses: $/path`, which act rejects
(nektos/act#6189) and pnpm run act:d depends on. The dangerous-triggers
finding on release.yml does not apply: it checks out main, never PR code.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 99.56% 679 / 682
🔵 Statements 99.56% 692 / 695
🔵 Functions 100% 167 / 167
🔵 Branches 94.51% 293 / 310
File CoverageNo changed files found.
Generated in workflow #2573 for commit 585d86d by the Vitest Coverage Report Action

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ No Changeset found

Latest commit: 585d86d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@andykenward
andykenward merged commit 9ea8a9a into main Oct 20, 2026
11 checks passed
@andykenward
andykenward deleted the chore/code-scanning-triage branch October 20, 2026 20:43
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.

1 participant