You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(dedupe): document the bare cwes (exact-set) hash token (F40)
The token table listed cwes_partial/cwes_subset but omitted the bare `cwes`
token (exact CWE set, folded into the hash like `vulnerability_ids`). Add the
row, note it in the exact-matching sentence, and include `cwes` in the
"CWE fields may not be the only criteria" rule.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/content/triage_findings/finding_deduplication/PRO__deduplication_tuning.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,10 +59,11 @@ Two finding attributes hold a *set* of values rather than a single value: vulner
59
59
|`vulnerability_ids`| they have the **exact same set** of vulnerability IDs |
60
60
|`vulnerability_ids_partial`| they share **at least one** vulnerability ID |
61
61
|`vulnerability_ids_subset`| one finding's vulnerability IDs are a **subset** of the other's |
62
+
|`cwes`| they have the **exact same set** of CWEs |
62
63
|`cwes_partial`| they share **at least one** CWE |
63
64
|`cwes_subset`| one finding's CWEs are a **subset** of the other's |
64
65
65
-
The `_partial` and `_subset` fields are compared per finding pair rather than folded into the hash: the remaining Hash Code Fields group the candidate findings, and the set comparison then narrows that group. (Exact matching, `vulnerability_ids`, is folded into the hash directly.)
66
+
The `_partial` and `_subset` fields are compared per finding pair rather than folded into the hash: the remaining Hash Code Fields group the candidate findings, and the set comparison then narrows that group. (Exact matching — `vulnerability_ids` and `cwes` — is folded into the hash directly.)
66
67
67
68
**Empty values.** If a finding has no vulnerability IDs (or no CWEs) for the configured matcher:
68
69
@@ -72,7 +73,7 @@ The `_partial` and `_subset` fields are compared per finding pair rather than fo
72
73
**Configuration rules** (enforced when you save settings):
73
74
74
75
- A vulnerability IDs field (`vulnerability_ids`, `vulnerability_ids_partial`, or `vulnerability_ids_subset`) may be used on its own — a CVE or GHSA identifies a specific vulnerability instance.
75
-
- CWE fields (`cwes_partial`, `cwes_subset`) may **not** be the only criteria. A CWE is a weakness *class*, not a specific instance, so matching on CWE alone would merge unrelated findings. Pair a CWE matcher with an identifying field such as `title` or `file_path`.
76
+
- CWE fields (`cwes`, `cwes_partial`, `cwes_subset`) may **not** be the only criteria. A CWE is a weakness *class*, not a specific instance, so matching on CWE alone would merge unrelated findings. Pair a CWE matcher with an identifying field such as `title` or `file_path`.
0 commit comments