Skip to content

fix(ci): allowlist lockfile sha256 hashes in gitleaks working-tree scan #1178

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.

Sign up for GitHub

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

Closed
groupthinking wants to merge 1 commit into from
Closed

fix(ci): allowlist lockfile sha256 hashes in gitleaks working-tree scan #1178

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion .gitleaks.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,17 @@
useDefault = true

[allowlist]
description = "Paths excluded from secret scanning"
description = "Paths and false-positive patterns excluded from secret scanning"
# Package lockfiles (uv.lock, package-lock.json, etc.) record public SHA-256
# package-integrity hashes. Their high entropy trips the default
# square-access-token rule (e.g. uv.lock:5129, the `parso` sdist hash), even
# though a `sha256:<hex>` integrity digest is not a credential. Match on the
# whole line so only genuine `hash = "sha256:..."` digests are allowlisted;
# any real token elsewhere in a lockfile is still scanned.
regexTarget = "line"
regexes = [
'''hash = "sha256:[0-9a-f]{64}"''',
]
paths = [
# Vendored saved web pages from Google (AI Studio / APIs Explorer): contain
# Google's own public page keys, not EventRelay credentials.
Expand Down
Loading