Adding a rule
Coverage should be a YAML file plus fixtures — not a Go change — whenever the rule schema is sufficient.Checklist
- Unique, stable
id(renaming breaks users’ SARIF baselines) - Canonical
primitivename that exists in the classifier - Honest
confidence—highonly when the match alone establishes primitive and parameters - Positive fixture that must match
- Negative fixture that must not (comment, test file, similar-looking non-crypto call)
-
referenceslink to authoritative documentation -
make lint-rulespasses; golden files regenerated deliberately