Skip to content

chore(security): ignore synthetic KDF test fixture in secret scans - #62

Merged
TheStreamCode merged 1 commit into
mainfrom
chore/gitleaks-test-fixture
Oct 31, 2026
Merged

TheStreamCode merged 1 commit into
mainfrom
chore/gitleaks-test-fixture

Conversation

@TheStreamCode

Copy link
Copy Markdown
Owner

Suppresses the generic-api-key findings for the hard-coded mock derived key in src/tests/services/AuthService.test.ts (lines 164, 603). The value is a visible repeating hex pattern used by two KDF test blocks; it cannot authenticate anything. Entries cover both history scans (commit-pinned, per the chutes-build precedent) and working-tree scans (bare path fingerprints). Verified locally: gitleaks detect reports no leaks in git mode and no findings in tracked files in --no-git mode; bun run test:ci passes (36 suites, 253 tests).

The AuthService suite hard-codes a mock derived key built from a visible repeating hex pattern. It trips the generic-api-key rule in both history and working-tree scans. Suppress the exact finding fingerprints; the value cannot authenticate anything.
@TheStreamCode
TheStreamCode merged commit 8c893ea into main Oct 31, 2026
5 checks passed
@TheStreamCode
TheStreamCode deleted the chore/gitleaks-test-fixture branch October 31, 2026 23:06
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