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

36 lines
No EOL
836 B
YAML

rules:
- name: Codacy API Key
id: kingfisher.codacy.1
pattern: |
(?xi)
\b
codacy
(?:.|[\n\r]){0,32}?
(?:SECRET|PRIVATE|ACCESS|KEY|TOKEN)
(?:.|[\n\r]){0,32}?
\b
(
[0-9A-Z]{20,24}
)
\b
pattern_requirements:
min_digits: 2
min_entropy: 3.5
confidence: medium
examples:
- codacySECRET=a1b2c3d4e5f6g7h8i9j0
- codacyACCESS_KEY k1l2m3n4o5p6q7r8s9t0
validation:
type: Http
content:
request:
headers:
Accept: application/json
api-token: '{{ TOKEN }}'
method: GET
response_matcher:
- report_response: true
- status:
- 200
type: StatusMatch
url: https://app.codacy.com/api/v3/user/organizations