kingfisher/data/rules/deepseek.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
974 B
YAML

rules:
- name: DeepSeek API Key
id: kingfisher.deepseek.1
pattern: |
(?xi)
\b
(
sk-[a-f0-9]{32}
)
\b
pattern_requirements:
min_digits: 2
min_entropy: 3.7
confidence: medium
examples:
- sk-ba588036180d4d1d9cebbf6456f1e220
- sk-2481fb3538a1453fac54f6cbdca981cb
- sk-8be2c2f8cf2e424aad1643c1d3944377
validation:
type: Http
content:
request:
method: GET
url: https://api.deepseek.com/models
headers:
Authorization: "Bearer {{ TOKEN }}"
Accept: application/json
response_matcher:
- report_response: true
- type: StatusMatch
status: [200]
- type: WordMatch
words: ['"data"']
match_all_words: true
references:
- https://api-docs.deepseek.com/
- https://api-docs.deepseek.com/api/list-models