-
-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): bump the actions group with 3 updates #60
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -28,7 +28,7 @@ jobs: | |
| find . -type f -perm /111 -name "*.sh" | head -10 || true | ||
|
|
||
| - name: Check for secrets | ||
| uses: trufflesecurity/trufflehog@v3.96.0 | ||
| uses: trufflesecurity/trufflehog@v3.97.1 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔴 HIGH RISK Pinning third-party actions to a full 40-character commit SHA ensures the workflow is immutable and protected against potential tag-moving or repository compromise. While version tags like v3.97.1 are readable, they are not cryptographically secure. Consider updating the uses statement to a commit SHA while keeping the version tag as a trailing comment. |
||
| with: | ||
| path: ./ | ||
| base: ${{ github.event.pull_request.base.sha || github.event.before }} | ||
|
|
||
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.
🔴 HIGH RISK
This update introduces a floating major version tag (@v18) which deviates from the repository's convention of pinning to specific patch versions or commit SHAs. Using a mutable tag is risky as it can change upstream, leading to unexpected behavior or security vulnerabilities. It is recommended to pin the action to a specific commit SHA to ensure the workflow remains immutable and protected against supply chain risks.
See Issue in Codacy