ci: pin trufflesecurity/trufflehog to a full commit SHA (v3.95.9) - #14685
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Pins the TruffleHog GitHub Action in the secret-scanning workflow to an immutable commit SHA to reduce CI supply-chain risk while keeping the human-readable version noted inline.
Changes:
- Replace
trufflesecurity/trufflehog@mainwith a full commit SHA pin - Preserve the release version (
v3.95.9) as a comment for maintainability
v-shukore
approved these changes
Jul 20, 2026
v-shukore
approved these changes
Jul 20, 2026
v-atulyadav
approved these changes
Jul 20, 2026
v-dvedak
approved these changes
Jul 20, 2026
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.
Hi, and thank you for Azure Sentinel.
Small CI supply-chain hardening, one line.
ScanSecrets.yamlruns the secret scanner from a mutable branch ref:The job carries
pull-requests: writeand checks out PR code, so whatevertrufflehog@mainhappens to point at executes with the repo'sGITHUB_TOKEN. A branch can move after review; a full commit SHA cannot (GitHub's own hardening guidance recommends SHA-pinning third-party actions).This PR pins it to the commit behind the current release, keeping the version visible as a comment:
Verified:
gh api repos/trufflesecurity/trufflehog/git/ref/tags/v3.95.9→27b0417c…. Behavior today is unchanged; future updates become a deliberate one-line bump (Dependabot can manage SHA pins, not branch refs).For transparency: I used AI assistance to spot and draft this; I verified the workflow content and the release SHA myself.