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
Copy file name to clipboardExpand all lines: docs/content/supported_tools/parsers/file/anchore_grype.md
+28Lines changed: 28 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -203,3 +203,31 @@ By default, DefectDojo identifies duplicate Findings using these [hashcode field
203
203
- severity
204
204
- component name
205
205
- component version
206
+
207
+
### Anchore Grype Detailed
208
+
209
+
Both scan types accept the same JSON report format. The difference is in how Findings are deduplicated:
210
+
211
+
-**`Anchore Grype`** — Aggregates all matches for the same CVE, component name, and version into a single Finding, regardless of file path. Deduplication is based on hashcode fields (`title`, `severity`, `component_name`, `component_version`).
212
+
-**`Anchore Grype detailed`** — Creates a separate Finding for each unique file path. Deduplication is based on `unique_id_from_tool`, composed as `{vuln_id}|{component_name}|{component_version}|{file_path}`.
213
+
214
+
A typical case is a package installed at multiple paths in a container image (e.g., /usr/lib/x86_64-linux-gnu/libc.so.6 and /lib/x86_64-linux-gnu/libc.so.6) — the same CVE would produce one Finding in default mode and two in detailed mode.
215
+
216
+
**Field mapping:**
217
+
218
+
| Finding Field | Grype JSON Source |
219
+
|---|---|
220
+
|`title`|`{vulnerability.id} in {artifact.name}:{artifact.version}`|
0 commit comments