-
Notifications
You must be signed in to change notification settings - Fork 0
ci(helios): Pin workflow dependencies #49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: ryancinsight/helios
Length of output: 13927
🌐 Web query:
actions/checkout persist-credentials false GITHUB_TOKEN .git/config README💡 Result:
The persist-credentials input in actions/checkout controls whether the action configures Git to use the repository's access token (such as GITHUB_TOKEN) for subsequent Git operations performed within the job [1][2]. Behavior by Version: - In versions prior to the recent refactor (typically v5 and earlier), setting persist-credentials: true (the default) caused the action to write the authentication token directly into the repository's.git/config file [3]. - In current versions (notably v6+), the action has been improved to store credentials in a separate file located under $RUNNER_TEMP instead of directly in.git/config [1][2]. It uses Git's includeIf mechanism to conditionally reference this file [4][3]. Security Context: - When persist-credentials is set to true (the default), the token persists on the runner disk until post-job cleanup, enabling downstream steps to execute authenticated Git commands [1][3]. - Setting persist-credentials: false opts out of this behavior, preventing the action from writing the token to either.git/config or the temporary file, thereby reducing the credential's exposure surface [1][3]. - Note that setting this to false only affects the "persistence" of the token into Git configuration; it does not change the fact that the GITHUB_TOKEN itself remains available as an environment variable to all steps within the job [5]. If your goal is to minimize security risks, it is a recommended best practice to set persist-credentials: false if your workflow does not require authenticated Git operations in later steps [3].
Citations:
persist-credentials: falseon checkout steps cli/go-gh#225persist-credentialsor change the default tofalseactions/checkout#485🏁 Script executed:
Repository: ryancinsight/helios
Length of output: 24116
🏁 Script executed:
Repository: ryancinsight/helios
Length of output: 2399
🏁 Script executed:
Repository: ryancinsight/helios
Length of output: 5555
🏁 Script executed:
Repository: ryancinsight/helios
Length of output: 9673
🏁 Script executed:
Repository: ryancinsight/helios
Length of output: 2957
Disable persisted credentials on every checkout.
actions/checkoutdefaultspersist-credentialstotrue. At this pinned version, it stores the token in$RUNNER_TEMPand adds a local Git configuration reference in each checkout. Later repository-controlled commands can access the token. Addpersist-credentials: falseto all six checkout steps. Use a separately scoped credential only when a later authenticated Git operation requires one.🧰 Tools
🪛 zizmor (1.29.0)
[warning] 122-125: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
📍 Affects 2 files
.github/workflows/ci.yml#L122-L125(this comment).github/workflows/book-pages.yml#L31-L31.github/workflows/ci.yml#L17-L19.github/workflows/ci.yml#L71-L73.github/workflows/ci.yml#L117-L120.github/workflows/ci.yml#L142-L146🤖 Prompt for AI Agents
Source: Linters/SAST tools