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

36 lines
879 B
YAML

rules:
- name: Gitter Access Token
id: kingfisher.gitter.1
pattern: |
(?xi)
\b
gitter
(?:.|[\n\r]){0,24}?
\b
(
[a-z0-9_-]{40}
)
\b
pattern_requirements:
min_digits: 2
min_entropy: 3.2
confidence: medium
examples:
- GITTER_TOKEN=abcd1234efgh5678ijkl9012mnop3456qrst7890
- '"gitterToken": "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0"'
references:
- https://developer.gitter.im/docs/authentication
validation:
type: Http
content:
request:
method: GET
url: https://api.gitter.im/v1/user
headers:
Authorization: 'Bearer {{ TOKEN }}'
Accept: application/json
response_matcher:
- report_response: true
- type: StatusMatch
status:
- 200