ci(check-secrets): exclude brand favicon SVGs from kingfisher (LC-471) #451

Merged
vas2000-work merged 2 commits from fix/LC-471-check-secrets-favicon-fp into main 2026-06-28 00:52:39 +02:00
Member

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

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>
ci(check-secrets): exclude brand favicon SVGs from kingfisher (LC-471)
Some checks failed
check-secrets / Nosey parker (push) Successful in 3s
check-secrets / Nosey parker (pull_request) Successful in 6s
check-secrets / TruffleHog (push) Successful in 4s
check-secrets / TruffleHog (pull_request) Successful in 7s
check-secrets / Kingfisher (push) Successful in 8s
check-secrets / Kingfisher (pull_request) Successful in 9s
Check / clippy + fmt + tests (pull_request) Failing after 2m30s
9700d271c2
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>
Merge branch 'main' into fix/LC-471-check-secrets-favicon-fp
All checks were successful
check-secrets / Nosey parker (push) Successful in 8s
check-secrets / Kingfisher (push) Successful in 10s
check-secrets / Nosey parker (pull_request) Successful in 11s
check-secrets / TruffleHog (push) Successful in 12s
check-secrets / TruffleHog (pull_request) Successful in 54s
check-secrets / Kingfisher (pull_request) Successful in 55s
Check / clippy + fmt + tests (pull_request) Successful in 5m30s
Create release / Create release from merged PR (pull_request) Has been skipped
f55d0d5769
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/lets-chat!451
No description provided.