kingfisher/data/rules/twitch.yml
Mick Grove c0e4910d1f 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

38 lines
No EOL
935 B
YAML

rules:
- name: Twitch API Token
id: kingfisher.twitch.1
pattern: |
(?xi)
\b
twitch
(?:.|[\n\r]){0,32}?
\b
(
[a-z0-9]{30}
)
\b
pattern_requirements:
min_digits: 2
min_uppercase: 1
min_lowercase: 1
min_entropy: 3.5
confidence: medium
examples:
- TWITCH_TOKEN=abcdefghijklmnopqrstuvwx123456
- "twitch_api_token: '0123456789abcdefghijklmnopqrstuv'"
references:
- https://dev.twitch.tv/docs/authentication/validate-tokens/
validation:
type: Http
content:
request:
method: GET
url: https://id.twitch.tv/oauth2/validate
headers:
Authorization: 'OAuth {{ TOKEN }}'
Accept: application/json
response_matcher:
- report_response: true
- type: StatusMatch
status: [200]
- type: JsonValid