ci(security): add blocking gitleaks secret scan - #15
Merged
Merged
Conversation
No workflow in this repository scans for secrets. Adds a job running gitleaks v8.30.1 over the working tree, with the binary verified against the release checksums, that fails the check on any finding. History is deliberately not scanned: a secret already committed needs rotating, not a permanently red pipeline. The first run shows what it finds; findings are reviewed and either removed or allowlisted with a reason in a follow-up commit. Refs: NOFireAI/engineering#910 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Stylianos Rigas <stylianosrigas@gmail.com>
stylianosrigas
marked this pull request as ready for review
September 14, 2026 12:15
panosmaurikos
approved these changes
Sep 14, 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
2 participants
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.
Summary
Adds a blocking secret scan. No workflow in this repository scans for secrets.
Same approach as NOFireAI/brain-go#3014 and NOFireAI/brain#1277. This PR starts
with the scan alone; the first run shows what it finds, and each finding is then
reviewed and either removed or allowlisted with a reason.
Notes
without
sudo.gitleaks-actionis avoided because it needs a licence keyfor organisations.
Refs: NOFireAI/engineering#910
🤖 Generated with Claude Code