Skip to content

fix(gitleaks): allowlist manifests/README.md false positive#59

Merged
lusoris merged 1 commit intomasterfrom
fix/gitleaks-manifests-readme-allowlist
Apr 19, 2026
Merged

fix(gitleaks): allowlist manifests/README.md false positive#59
lusoris merged 1 commit intomasterfrom
fix/gitleaks-manifests-readme-allowlist

Conversation

@lusoris
Copy link
Copy Markdown
Owner

@lusoris lusoris commented Apr 19, 2026

Summary

  • Adds one path entry to .gitleaks.toml allowlist: ^ai/src/vmaf_train/data/manifests/README\.md$
  • Silences a generic-api-key false positive where the rule flagged a YAML example (- key: src01_hrc00_576x324) as a secret
  • Only a documentation file — shows the YAML manifest schema, never contains real manifests

Why now

Surfaced by PR #58's ours-merge, which expanded the gitleaks scan range (--first-parent 966be8d5^..<merge>) to every fork commit since divergence. Regular PR-diff-only scans missed it because the file was unchanged in those PRs.

Test plan

  • Gitleaks job passes on this PR
  • No other .md in ai/src/vmaf_train/data/manifests/ exists yet that would be accidentally masked

🤖 Generated with Claude Code

The `generic-api-key` rule flags `  - key: src01_hrc00_576x324` in
ai/src/vmaf_train/data/manifests/README.md line 20 because "key:" +
an entropic token (a public Netflix VMAF sample name) matches its
heuristic. That README is documentation showing the YAML manifest
format, not a manifest itself — no real secrets live there.

Only surfaced now because PR #58's ours-merge expanded the gitleaks
scan range (`--first-parent 966be8d^..<merge>`) to every fork commit
since divergence. Prior PR-diff-only scans never touched this file.

Add an explicit path allowlist entry (not a regex/stopword) so future
edits to real manifest files still get scanned.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@lusoris lusoris merged commit 5786a70 into master Apr 19, 2026
42 checks passed
@lusoris lusoris deleted the fix/gitleaks-manifests-readme-allowlist branch April 19, 2026 19:11
@github-actions github-actions Bot mentioned this pull request Apr 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant