Skip to content

fix(security): canonical gitleaks allowlist config (P71)#1

Merged
jcrabtree merged 1 commit into
masterfrom
fix/gitleaks-broken-allowlist
May 18, 2026
Merged

fix(security): canonical gitleaks allowlist config (P71)#1
jcrabtree merged 1 commit into
masterfrom
fix/gitleaks-broken-allowlist

Conversation

@jcrabtree

Copy link
Copy Markdown

Summary

Replaces the broken [[rules]] tags=["allowlist"] pattern with the canonical
Magnon [allowlist] config. The old rule was a detection rule that fired on
common substrings (test, fake, example, placeholder, dummy, sample) and
produced a false-positive storm.

Reference

Aligns with Project-Aethra/aethra#6 and the P58/P71 estate-wide sweep.

Test plan

  • gitleaks detect --config .gitleaks.toml --no-banner passes locally
  • CI gitleaks scan stays green

…al config

The previous .gitleaks.toml used a [[rules]] block with tags=["allowlist"]
to try to suppress false positives. That is a DETECTION rule that fires on
test|fake|example|placeholder|dummy|sample anywhere in a string, causing a
false-positive storm on data-testid, testing-library, :latest tags,
samplerArg, etc.

Gitleaks tags are metadata only — they do not silence rules. The correct
suppression mechanism is `[allowlist]` (top-level) or `[[rules]].allowlist`
(per-rule). This commit replaces the broken file with the canonical Magnon
template approved in Project-Aethra/aethra#6.

Refs: P58/P71 gitleaks rule-as-allowlist fix sweep
@jcrabtree jcrabtree merged commit 535fbb5 into master May 18, 2026
0 of 17 checks passed
@jcrabtree jcrabtree deleted the fix/gitleaks-broken-allowlist branch May 18, 2026 14:35
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