kingfisher/data/rules/beamer.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

37 lines
No EOL
886 B
YAML

rules:
- name: Beamer API token
id: kingfisher.beamer.1
pattern: |
(?xi)
\b
beamer
(?:.|[\n\r]){0,64}?
\b
(
b_[A-Z0-9=_\\/\\\-+]{44}
)
\b
pattern_requirements:
min_digits: 2
min_uppercase: 1
min_lowercase: 1
min_entropy: 3.0
confidence: medium
examples:
- beamer = b_ByDfulghxvvmHbArJSFfQhxemJPQHOwplxuydlKEEbfe
- "BEAMER_key = 'b_ByDfulghxvvmHbArJSFfQhxemJPQHOwplxuydlKEEbfe'"
references:
- https://getbeamer-api.pages.dev/
validation:
type: Http
content:
request:
headers:
Beamer-Api-Key: '{{ TOKEN }}'
method: GET
response_matcher:
- report_response: true
type: WordMatch
words:
- '"name":'
url: https://api.getbeamer.com/v0/ping