Add betterleaks secret scanning - #85
Closed
repowarden-app[bot] wants to merge 1 commit into
Closed
Conversation
![repowarden[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
Co-Authored-By: repowarden[bot] <bot@repowarden.dev>
Author
|
This PR has been open for 14 days without being merged, so I'm closing it. If there was an issue with these changes, please reply with feedback so I can improve! — RepoWarden |
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.
What this adds
.github/workflows/betterleaks.yml— runs betterleaks on every push and PR so new secrets can't sneak in..betterleaks.toml— extends the betterleaks defaults with an allowlist for the usual false-positive offenders (test env files, GTM/analytics IDs, fixtures, snapshots, .NET test projects).Betterleaks is the free, open-source successor to gitleaks (built by the same maintainers). The CI step takes a few seconds and fails the build if it finds anything — so this catches mistakes before they hit the default branch.
Existing findings
None — your working tree is clean.