ci(check-secrets): exclude brand favicon SVGs from kingfisher (LC-471) #451
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/LC-471-check-secrets-favicon-fp"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The LC-470 landing-page redesign rebuilt server/assets/favicon.svg and favicon-dot.svg as an SVG wrapping a base64-encoded PNG raster. A substring of that base64 blob (CIo5WSqz7HzuYM41D1E0cwpOXjiVktTfRru) matches the KINGFISHER.CRATESIO.1 rule, so kingfisher reports it as a (false-positive) crates.io API key and exits non-zero, failing check-secrets.yml on every commit since
b6a4261. TruffleHog (--only-verified) and Nosey Parker do not flag it; kingfisher is the only failing job.Add both brand assets to kingfisher's existing --exclude list, alongside .sops.yaml and the *-secrets globs, with a comment naming the false positive. The path exclude also covers the files' history blobs, so --git-history full stays green. These are bundled brand images, not a secret-bearing surface, so excluding them from secret scanning carries no real risk.
#LC-471
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com