-
Notifications
You must be signed in to change notification settings - Fork 7
Expand file tree
/
Copy path.gitleaks.toml
More file actions
35 lines (33 loc) Β· 2.18 KB
/
Copy path.gitleaks.toml
File metadata and controls
35 lines (33 loc) Β· 2.18 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
title = "WorldScript Studio gitleaks config"
[extend]
# QNBS-v3: keep every default gitleaks rule active β this file only narrows one verified false
# positive, it does not weaken secret detection anywhere else in the repo.
useDefault = true
# βββ Verified false positives ββββββββββββββββββββββββββββββββββββββββββββββββ
#
# PASSPHRASE_SENTINEL_RECORD_KEY = 'idb_passphrase_sentinel_v1'
# (services/storage/idbPassphraseSentinel.ts, mirrored as a mock constant in
# tests/unit/storageEncryptionService.test.ts) is a static IndexedDB record-key identifier, not a
# credential β the app must know it deterministically to find the passphrase-sentinel record via
# store.get/put/delete. Gitleaks' `generic-api-key` heuristic flags it purely because the variable
# name contains "PASSPHRASE" + "KEY" next to a sufficiently long, structured string (entropy 3.72).
# Reviewed 2026-08-12: no other gitleaks finding in this scan; pnpm audit / OSV / CodeQL all clean.
#
# gitleaks' top-level [allowlist] has no AND condition between `paths` and `regexes` (only
# per-rule [[rules.allowlists]] blocks support `condition`), so combining both here would OR them β
# broadening the exemption to "anything in that file" rather than narrowing it. The exact leaked
# value alone is already a highly-specific, non-generic string that cannot coincidentally match a
# real secret elsewhere, so it's the narrowest correct scope available in this schema.
#
# apt-cef-harness-deps-v1 / apt-tauri-linux-deps-v1
# (.github/workflows/cef-learning-harness.yml, ci.yml) are actions/cache `key:` values for apt
# archive caching β static, non-secret cache-namespace strings. Flagged by the same generic-api-key
# heuristic: YAML `key:` field name next to a hyphenated alphanumeric string. Reviewed 2026-08-19:
# both are cache keys with a fixed literal suffix (`-v1`), not credentials.
[allowlist]
description = "Cache-key / record-key literals flagged by generic-api-key's key-adjacent-string heuristic β not credentials"
regexes = [
'''^idb_passphrase_sentinel_v1$''',
'''^apt-cef-harness-deps-v1$''',
'''^apt-tauri-linux-deps-v1$''',
]