Glossary
- Accepted
-
The state of an entry that is
affected, hasdisposition: wont fix, and has no resolution. See States. - Alias
-
Another ID of the same vulnerability, for example its GHSA ID, listed in
aliases. See Vulnerabilities. - Analysis
-
The reasoning behind a verdict, recorded in
analysis. See Vulnerabilities. - Canonical style
-
The one layout in which Vulnlog commands write a Vulnlog file. See vulnlog fmt.
- Disposition
-
What you plan to do about a vulnerability that affects you:
will fixorwont fix. See Verdicts and justifications. - Entry
-
A vulnerability recorded in the
vulnerabilitieslist of a Vulnlog file. See Vulnerabilities. - Finding
-
A vulnerability that a scanner reports. See Vulnlog and your scanner.
- Generic suppression file
-
A JSON suppression file, named
<reporter>.generic.json, that Vulnlog writes for reporters without a native format. See Supported scanners. - Impact report
-
An HTML page that shows which releases each vulnerability affects, how severely, and its state. See vulnlog report impact.
- Justification
-
The reason a vulnerability doesn’t affect your software, required with
verdict: not affected. See Verdicts and justifications. - Not applicable
-
The state of an entry that is
not affectedand has no resolution. See States. - Open
-
The state of an entry that is
affected, has no resolution, and isn’t markedwont fix. See States. - OpenVEX
-
A JSON format for VEX statements. Vulnlog’s OpenVEX output is incubating. See vulnlog vex openvex.
- Package URL (PURL)
-
A standard identifier for a software package, for example
pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1. See Project and releases. - Project
-
The organisation, project name, and author of a Vulnlog file, recorded in
project. See Project and releases. - Release
-
A version of your software that the Vulnlog file tracks, listed in
releases. See Project and releases. - Release notes
-
A list of the vulnerabilities a release fixes, generated with
vulnlog report changelog. See vulnlog report changelog. - Report
-
An item in an entry’s
reportslist that names the scanner or source that reported the vulnerability, and when. See Report. - Reporter
-
The scanner or other source in a report, for example
trivyorother. It decides which suppression file the entry goes into. See Supported scanners. - Resolution
-
The release that fixes a vulnerability, recorded in
resolution. See Vulnerabilities. - Resolved
-
The state of an entry with a verdict and a resolution. See States.
- Schema header
-
The optional first-line comment that points editors to the Vulnlog JSON schema. See File format.
- Severity
-
How severe a vulnerability is for your software:
low,medium,high, orcritical. See Verdicts and justifications. - State
-
A label that Vulnlog derives from an entry’s verdict, disposition, and resolution. See States.
- Suppression
-
Listing a finding in a suppression file so that the scanner ignores it, permanently or until a date. See Suppression.
- Suppression file
-
A file that Vulnlog generates so a scanner ignores a finding, for example
.trivyignore.yaml. See Suppression. - Tag
-
A label you define in
tagsand attach to entries and release PURLs. See Tags. - Under investigation
-
The state of an entry without a verdict. See States.
- Verdict
-
Your judgement whether a vulnerability affects your software:
affectedornot affected. See Verdicts and justifications. - VEX
-
Vulnerability Exploitability eXchange, a machine-readable statement of whether a vulnerability affects a product. See Vulnlog and VEX.
- Vulnlog file
-
A YAML file in the Vulnlog format, for example
acme-shop.vl.yaml. See File format.