Skip to content

chore(ci): gitleaks passes the release key's public fingerprint - #40

Merged
HackTuah merged 1 commit into
mainfrom
chore/gitleaks-release-fingerprint
Oct 7, 2026
Merged

HackTuah merged 1 commit into
mainfrom
chore/gitleaks-release-fingerprint

Conversation

@HackTuah

@HackTuah HackTuah commented Oct 7, 2026

Copy link
Copy Markdown
Member

The security review report in #39 quotes the release key's public SSH fingerprint (SHA256:HqIaFq…) from the reviewers' reports, and gitleaks reads it as a generic API key. The fingerprint is public by design: it is in MAINTAINERS.md and .github/allowed_signers. This adds it as a stopword. Since #28 a pull request can't allowlist its own findings, so this lands on main first.

Lead check: with this config, CI's scan command finds no leaks on #39's branch.

🤖 Generated with Claude Code

The security review report (#39) quotes the release key's SSH fingerprint
from the reviewers' reports, and gitleaks reads it as a generic API key.
It is public by design (MAINTAINERS.md, .github/allowed_signers). Since
#28 a pull request can't allowlist its own findings, so this lands first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Ayla Croft <dev@scriptkittyos.com>
@HackTuah
HackTuah requested a review from minitru as a code owner October 7, 2026 23:06
@HackTuah
HackTuah merged commit 4929e34 into main Oct 7, 2026
12 checks passed
@HackTuah
HackTuah deleted the chore/gitleaks-release-fingerprint branch October 7, 2026 23:26
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