Remove the scan information section

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
alexanderandClaude Opus 5.5 committed 2026-09-24 21:14:14 +02:00
1 parent b380c736c9
commit 9d78e9edf4
5 files changed
+6 -184

No files matched your search

+4 -5
View File
@@ -39,8 +39,8 @@ report_generator from-folder --artifacts ./sample [--path <file-or-directory>]
whose metadata is gone.
The inputs are one SARIF file (`merged.sarif`, with one run per tool) and the vulnerability report
(`vdr.json`); either is enough on its own. `metadata.json` is optional, and without it the scan and
project pages are left out. The report has these parts:
(`vdr.json`); either is enough on its own. `metadata.json` is optional, and without it the project
page is left out. The report has these parts:
1. the cover and a table of contents,
2. a summary and the most critical issues across all sources,
@@ -98,9 +98,8 @@ vectors by `persistent_storage.utils.cvss_utils`.
### What it cannot fill in
A field the artifacts do not answer is written as `<xxx>`, never guessed or quietly dropped. Today
that is the manufacturer (unless given with `--manufacturer`), the analysed lines of code, the language
breakdown, and the tools and profile of each pipeline stage — the metadata records that a stage ran
and how long it took, not what it ran.
that is the manufacturer (unless given with `--manufacturer`), the analysed lines of code and the language
breakdown.
A measured zero survives: `0 filtered` is a reading, and a blank is a gap.