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

40 lines
No EOL
1 KiB
YAML

rules:
- name: Tavily API Key
id: kingfisher.tavily.1
pattern: |
(?x)
\b
(
tvly-[a-zA-Z0-9]{32}
)
\b
pattern_requirements:
min_digits: 2
confidence: medium
min_entropy: 3.0
references:
- https://docs.tavily.com/api-reference
examples:
- "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"
- "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"
- 'TAVILY_API_KEY = "tvly-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"'
validation:
type: Http
content:
request:
method: POST
url: "https://api.tavily.com/search"
headers:
Authorization: "Bearer {{TOKEN}}"
Content-Type: "application/json"
body: '{"query": "test"}'
response_matcher:
- report_response: true
- type: StatusMatch
status: [200]
- type: WordMatch
words:
- '"query":'
- '"results":'
match_all_words: true