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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
What is the official commit SHA for the latest stableactions/checkoutv6 release, and does its README documentpersist-credentialsdefault behavior and security implications?💡 Result:
The latest stable release of
actions/checkoutas of June 1, 2026, is v6.0.2 [1]. The commit SHA forv6.0.2is 11bd70f011116c478a87693246313203f56b7c5e. Regardingpersist-credentials: - The README explicitly documents thepersist-credentialsinput [2][3]. - Its default behavior istrue, meaning the action configures the authentication token (or SSH key) with the local git config to enable authenticated git commands [2][3]. - In v6, the action has been updated to improve security: instead of storing credentials directly in.git/config, they are now stored in a separate file under$RUNNER_TEMP[2][4][3]. - While the README highlights this as "improved credential security" [2][3], it acknowledges that the token remains available to subsequent steps in the job [2]. Users who wish to disable this behavior can explicitly setpersist-credentials: false[2][3].Citations:
Pin
actions/checkoutand disable persisted credentialsLine 37 uses mutable
actions/checkout@v6, which weakens supply-chain guarantees; hard-pin to the v6.0.2 commit SHA. Also disable credential persistence since this workflow doesn’t need authenticated git credentials for later steps.🔐 Proposed hardening patch
📝 Committable suggestion
🧰 Tools
🪛 zizmor (1.25.2)
[warning] 36-37: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
[error] 37-37: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)
(unpinned-uses)
🤖 Prompt for AI Agents