-
Notifications
You must be signed in to change notification settings - Fork 163
ci: update bashunit GitHub action using dependabot #545
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 all commits
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 | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: wfxr/forgit
Length of output: 4735
🏁 Script executed:
Repository: wfxr/forgit
Length of output: 4410
Pin the third-party action to a full commit SHA.
verify-checksumverifies the downloaded bashunit binary, not the composite action files. Replace the mutableTypedDevs/bashunit@0.40.0tag with the full commit SHA for the intended release.🧰 Tools
🪛 zizmor (1.29.0)
[warning] 3-113: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
[warning] 18-70: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
🤖 Prompt for AI Agents
Source: MCP tools
🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: wfxr/forgit
Length of output: 4668
🏁 Script executed:
Repository: wfxr/forgit
Length of output: 5670
🌐 Web query:
GitHub Actions workflow permissions default GITHUB_TOKEN permissions unspecified permissions key actions/checkout contents read official documentation💡 Result:
In GitHub Actions, the default permissions for the GITHUB_TOKEN are determined by repository or organization settings [1][2]. By default, when creating a new repository in a personal account, the GITHUB_TOKEN is granted read access to the contents and packages scopes [1]. Administrators can configure this default behavior in repository or organization settings to either a restricted set of permissions (read-only for contents and packages) or more permissive settings [1][3]. When you define a permissions key in your workflow file (at the workflow or job level), it overrides the default settings [2][4]. A critical rule in GitHub Actions is that if you specify any permissions in the permissions key, all other permissions not explicitly listed are set to none [2][5][6]. Consequently, if a job requires multiple types of access, you must explicitly define each one within the permissions block [2]. Regarding the official recommendation for the actions/checkout action, it requires read access to the repository's contents to function correctly (unless alternative authentication is provided) [7][8]. Therefore, if you are explicitly setting permissions for a job that uses actions/checkout, you should include the following configuration [7][9]: permissions: contents: read This ensures the action has the necessary access to fetch your code while adhering to the principle of least privilege [10][4].
Citations:
Set workflow-level
permissionstocontents: read..github/workflows/ci.yamlhas nopermissionsdeclaration, so repository or organization defaults apply.actions/checkoutneedscontents: read, and no job needs write access. TheTypedDevs/bashunit@0.40.0action does not consumeGITHUB_TOKEN.🧰 Tools
🪛 zizmor (1.29.0)
[warning] 3-113: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
[warning] 18-70: overly broad permissions (excessive-permissions): default permissions used due to no permissions: block
(excessive-permissions)
🤖 Prompt for AI Agents
Sources: MCP tools, Linters/SAST tools