fix: exclude false-positive paths from TruffleHog scanning #1
No files matched your search
@@ -36,8 +36,11 @@ jobs:
|
||||
- name: Run TruffleHog
|
||||
# --sarif outputs SARIF to stdout; redirect to file (no --output flag)
|
||||
# --fail exits 183 if secrets found; continue-on-error makes non-blocking
|
||||
# --exclude-paths uses .trufflehog-exclude.txt to skip files/paths
|
||||
# that routinely produce false positives (e.g. .git/ metadata,
|
||||
# Pi-hole blocklists with domain-name patterns matching secret detectors)
|
||||
run: |
|
||||
trufflehog filesystem . --sarif --fail --no-update > results.sarif
|
||||
trufflehog filesystem . --sarif --fail --no-update -x .trufflehog-exclude.txt > results.sarif
|
||||
continue-on-error: true
|
||||
|
||||
- name: Upload TruffleHog results to GitHub Security tab
|
||||
|
||||
@@ -0,0 +1,14 @@
|
||||
# TruffleHog exclude paths — patterns are matched as regex against file paths.
|
||||
# Each line is a separate regex pattern.
|
||||
|
||||
# Exclude the .git directory — it is git metadata, not tracked source.
|
||||
# TruffleHog can find credentials (e.g. tokens in .git/config from CI checkout)
|
||||
# that are not part of the repository content.
|
||||
.git/.*
|
||||
.git$
|
||||
|
||||
# Exclude Pi-hole blocklist files — they contain domain names from public
|
||||
# blocklists that routinely match secret detector patterns (e.g. hex strings
|
||||
# in subdomains matching Datadog API key/token detectors). These are data
|
||||
# files, not source code, and no real secrets should be stored here.
|
||||
pihole/combined_list\.txt
|
||||
Reference in new issue
Block a user