Repository navigation
Run online zizmor audits with a locked wheel - #61
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Install zizmor 1.31.1 from a dedicated dependency group. The lock records SHA-256 digests for its ten wheels and source archive. CI uses
uv sync --locked --only-group zizmor --no-buildso the scan executes the locked wheel.The scan now runs online audits with the built-in GitHub token and the workflow's
contents: readpermission. Only the scan step receivesGH_TOKEN. Strict collection still covers workflows and composite actions.Local resolution and a clean wheel-only install used the host's configured registry. The lockfile keeps the repository's public registry URLs and all existing dependency records. GitHub Actions validates the committed lockfile on the runner.