kingfisher/data/rules/gocardless.yml
Mick Grove 0f953f59a5 pattern_requirements for rules — Post-regex character-class gating to cut false positives without lookarounds. Authors can now require minimum counts of digits, uppercase, lowercase, and special characters, with an optional custom special-char set.
Why: Hyperscan doesn’t support lookaheads/behinds, so many “must contain X and Y” checks had to be baked into the regex (hurting readability) or were impossible. pattern_requirements applies lightweight, in-memory checks after a match is found, keeping patterns fast and clean.
2025-11-04 13:55:31 -05:00

44 lines
No EOL
1.1 KiB
YAML

rules:
- name: GoCardless API Token
id: kingfisher.gocardless.1
pattern: |
(?xi)
\b
gocardless
(?:.|[\n\r]){0,16}?
\b
(
live_
[A-Z0-9=_-]{16}
(?:[A-Z0-9=_-]{8}){3}
[A-Z0-9=_-]{0,2}
)
\b
pattern_requirements:
min_digits: 2
min_uppercase: 1
min_lowercase: 1
min_entropy: 3.5
confidence: medium
examples:
- 'gocardless_token = "live_8uq9fsUA28SqKT=CTsQxgKrqB6_7QV5tA39I8y5H'
- GOCARDLESS_LIVE_KEY = "live_cpo0k9jbnb2djeaq=tga45ua_bnhev5ivv294a6cs"
categories:
- api
- payment
- identifier
validation:
type: Http
content:
request:
headers:
Authorization: Bearer {{ TOKEN }}
Accept: application/json
GoCardless-Version: "2015-07-06"
method: GET
response_matcher:
- report_response: true
- status:
- 200
type: StatusMatch
url: https://api.gocardless.com/customers?limit=1