Auditing Findings
Description
ReARM aggregates security and compliance findings from your release artifacts and provides a structured workflow to triage, document, and suppress them. Findings are grouped into three types:
- Vulnerability - a known CVE or security vulnerability in a dependency
- Violation - a policy violation (license, security, or operational) detected by Dependency-Track
- Weakness - an integration or a code-level weakness identified for example by a SAST or DAST tool (CWE-based)
This page covers how to view, triage, and manage all finding types. For license-specific setup and viewing, see License Compliance. For bulk-applying triage decisions from VEX (Vulnerability Exploitability eXchange) documents — vendor-supplied or self-authored — see Importing VEX.
Where Findings Appear
Overview
Findings are displayed in multiple places throughout the ReARM interface to provide comprehensive visibility and management capabilities. Usually findings are shown per release or per artifact using colored circles. Each component row displays colored circles for:
- Critical / High / Medium / Low / Unassigned vulnerabilities
- License violations
- Security violations
- Operational violations
Click any circle to open the Findings Modal for that release or artifact, pre-filtered to the selected severity or violation type.
On the release page, the circles are followed by:
- a KEV circle that counts known exploited vulnerabilities;
- CVSS and EPSS pills with the release's highest score and highest exploit probability. Click a pill to open the Findings Modal sorted by that column.
How a Vulnerability's Severity Is Chosen
Several sources can rate one vulnerability, and they can disagree. ReARM takes the severity from the first of these that gives one:
- A triage analysis that sets a severity (the narrowest scope wins: release, branch, component, organization)
- NVD
- GitHub Advisories
- OSV
- VulnDB
- Any other source
The release counts, filters and approval conditions use this order. Vulnerability notifications use the same order of sources (2 to 6); your analyses then set the severity they are routed on, the narrowest scope first (see Notifications). A source that gives no severity, or Unassigned, gets one from its own CVSS score (or from its vector when no score is given) before the next source is asked, from CVSS v4, else v3, else v2: 9.0-10.0 is Critical, 7.0-8.9 High, 4.0-6.9 Medium, 0.1-3.9 Low; CVSS v2 has no Critical, so 7.0-10.0 is High there. When one source has several advisories for the vulnerability, the most severe one counts. In the Findings Modal, hover the info icon next to a vulnerability's severity to see each source's rating in this order (GitHub shows as GHSA).
Dashboard (Home)
The Home dashboard shows findings in several locations:
- Findings Over Time - Shows the trend of findings over time for the whole organization. Findings here are shown using a line chart with points for each day. Points are clickable and would open the Findings Modal for that specific day filtered by the selected severity or violation type.

- Most Vulnerable Components Widget - Shows the components with the highest finding counts in your organization.

- Most Recent Releases Widget - Shows the most recent releases in your organization.

Findings Modal
The Findings Modal is accessible from release views, component views, and the dashboard. It shows a combined table of all findings for a given scope. Each row includes:
- Type tag - Vulnerability, Violation, or Weakness
- Issue ID - CVE ID, CWE ID, or violation type (i.e. "LICENSE").
- Clicking a vulnerability ID opens its details; other IDs link to the upstream advisory where applicable.
- A KEV tag marks a CISA Known Exploited Vulnerability.
- PURL or Location - PURL of the dependency or code location
- Severity tag (for vulnerabilities and weaknesses)
- Score - the finding's headline CVSS score: CVSS v4, else v3, else v2.
- Hover to see all of the finding's scores.
- A computed tag means the source published only a vector, and ReARM calculated the score from it.
- EPSS - the probability that the vulnerability is exploited in the next 30 days, from FIRST's Exploit Prediction Scoring System. Hover for its percentile.
- Fixed in - the version that fixes the finding; see Fix Versions
- Details - additional details about the finding, including aliases alternative IDs (e.g., GHSA aliases for CVEs), reported License for License violations
- Sources - list of sources that reported the finding (specific Releases and Artifacts where finding was discoverd)
The switches above the table filter it:
- Show Suppressed and Show Unsuppressed - suppressed findings (state
FALSE_POSITIVEorNOT_AFFECTED) are shown as strikethrough. - KEV Only - only known exploited vulnerabilities.
- Has Fix - only findings whose advisory names a version that fixes them.
- Group by Component - one row per component; see Grouping by Component. ReARM remembers the choice.
Use Export to download the findings as a PDF report or as a CycloneDX 1.6 BOV (JSON) document.

Fix Versions
The Fixed in column comes from the affected version ranges in the vulnerability's advisories. ReARM fetches them from Dependency-Track when it first stores the vulnerability, and refreshes them nightly.
- For each finding, ReARM places the package's version within the ranges for that package, using the package ecosystem's version ordering. This is the same library Dependency-Track uses.
- For a Debian package, only the ranges for the finding's own Debian release count.
A cell shows:
| Cell | Meaning |
|---|---|
a version, e.g. 2.17.1 | The advisory says this version fixes the finding. |
> 2.4.1 | The advisory says versions up to 2.4.1 are affected, and names no fixed version. |
no fix yet | The advisory names no fixed version yet for this package. |
- | No fix version could be read. Hover for the reason: the advisory has no ranges for this package yet, the version is outside the advisory's affected ranges (the finding matched by name only), or the version cannot be placed in the ranges. |
Hover over a cell to see the sources (for example, GitHub or OSV) whose ranges gave the answer.
Grouping by Component
With Group by Component on, the table shows one row per affected component, with:
- its findings by severity;
- the worst score and the highest EPSS among them;
- the Bump to version;
- its KEV count and total.
Expand a row to see its findings. Column filters still apply to the findings inside each group, and the line above the table says which filters are active.
Bump to is the one version of the component that fixes the most of the group's findings, for example 5.2.17 fixes 32 of 32.
- How the count works:
- ReARM checks each candidate version against every advisory for the component. A version fixes a finding only when it is outside all of that finding's affected ranges, not merely past the fix the finding lists.
- The count covers the findings the filters leave visible.
- Leaving the current major version: when the bump does, a second line shows the best version that stays on it, for example
within 2.x: 2.2.24 fixes 18. When no version on the current major fixes any of them, it showsno fix on 19.x. - What stays affected: hover over the cell to see the findings the bump leaves affected, grouped by reason, such as no fix yet or no range data.
- Which findings it fixes: in the expanded findings, a check mark next to the Fixed in version marks each finding the bump fixes.
Vulnerability Details
Click a vulnerability's Issue ID, or an alias in Details, to open its details panel. It shows:
- the title and description;
- every score (CVSS, EPSS, OWASP Risk Rating) with its vector, sub-scores and source;
- the CWEs;
- the publication dates, aliases and references.
The panel also covers the affected versions and the finding's fix:
- Affected versions lists, for each package, the affected versions as a vers range, with a copy button and the sources that publish it. Show source bounds shows the ranges as each source wrote them.
- When the panel is opened from a finding's Issue ID, This finding shows the finding's package and its fix version.
- The package ranges that fix came from are tagged this finding.
- Opened from an alias, the panel leaves this line out, because the finding's fix comes from its own record.
- Users with write access to the organization can click Refresh from Dependency-Track to fetch the record again, affected versions included.
Changelogs
Findings are present in various changelogs across the application, including:
- Release changelogs
- Component changelogs
- Organization-wide changelog on the home page
- Perspective-wide changelog on the home page (ReARM Pro only)
Finding Analysis Page
The Finding Analysis page (accessible from the main navigation using the bug icon) provides a centralized table of all analysis records. Use this view to audit triage progress and manage findings across all components, branches, and releases. This table may be filtered by component, branch, release, or perspective (ReARM Pro only).

Auditing (Triaging) Findings (Creating an Analysis)
To triage a finding, create a Finding Analysis record. This documents your organization's assessment of the finding and optionally suppresses it from active counts.
ReARM supports multiple analysis records for the same finding per different scopes. A broader scope covers all narrower scopes within it. When filters are active in the Finding Analysis view, only the scopes that do not already have an analysis record are offered when creating a new one. Those scopes are:
| Scope | Applies To |
|---|---|
| Organization | All components and releases in the org |
| Component / Product | All branches and releases of a specific component |
| Branch / Feature Set | All releases on a specific branch |
| Release | One specific release only. Note, however, that this would propagate accordingly to any bundle that this release is a part of |
A Finding Analysis record can be created from the Findings Modal or from the Finding Analysis page.
- Creating from the Findings Modal
- Click the edit icon next to any finding in the Findings Modal. This opens the "Finding Analysis Records" dialog. It may have existing records if previuos analysis were made for this specific issue ID and location. If such records exist you may click on the edit icon in the Actions column to update analysis. Note that previous analysis would be preserved as well for audit purposes.
- If there are available scopes, you will see Add Scope button at the bottom of the dialog. Click it to add a new scope to the analysis.
- Creating from the Finding Analysis page
- In the Finding Analysis page, available scopes are based on the filters selected for findings. I.e., if no filters are chosen for Component/Product, you will only have access to Organization-wide scope. If filters are chosen for Component/Product, you will have access to this specific Component or Product and Organization-wide scopes. If filters are chosen also for Branch/Feature Set, you will have access to this specific Branch/Feature Set, Component/Product and Organization-wide scopes. If filters are chosen also for Release, you will have access to this specific Release, Branch/Feature Set, Component/Product and Organization-wide scopes.
- Click the edit icon next to any finding in the Finding Analysis view. If no analysis exists yet, this opens the Create Finding Analysis dialog. If an analysis already exists, it opens the Update dialog. If an analysis exists and there are available scopes, you will see plus icon next to the analysis record. Click it to add a new scope to the analysis.

Analysis Fields
When creating or updating a finding analysis, you will be able to work with the following fields:
| Field | Description |
|---|---|
| Finding ID | The CVE, CWE, or violation identifier - pre-filled, read-only |
| Finding Aliases | Alternative IDs - pre-filled from SBOM data, editable |
| Finding Type | VULNERABILITY, VIOLATION, or WEAKNESS - pre-filled |
| Location | PURL of the affected dependency or code path - pre-filled |
| Location Type | PURL or CODE_POINT - auto-detected |
| Scope | Level at which the analysis applies (see below) |
| Analysis State | Your triage decision (see below) |
| Justification | Reason for the decision - may be mandatory (see Admin Settings) |
| Severity | Optional severity override |
| Details | Free-form notes |
Analysis States
| State | Tag Color | Meaning |
|---|---|---|
| In Triage | Warning | Under review, no decision yet |
| Exploitable | Error | Finding is confirmed and actively exploitable |
| False Positive | Success | Finding does not apply, should not have been reported in the first place - suppresses the finding |
| Not Affected | Info | Component is not affected - suppresses the finding |
Findings in FALSE_POSITIVE or NOT_AFFECTED state are suppressed and excluded from active finding counts.
Managing Existing Analysis Records
From the Finding Analysis view, each record can be:
- Updated - change state, justification, severity, or details via the edit icon
- Expanded - view the full history of state changes, each with timestamp, state, justification, severity, and details
For Vulnerability type findings, an additional eye icon allows you to view all releases in the organization affected by the same CVE, helping prioritize remediation.
Filtering the Finding Analysis View
The Finding Analysis view supports the following filters:
- Type - Vulnerability, Violation, or Weakness
- Component / Product - filter to a specific component or product
- Branch / Feature Set - filter to a specific branch
- Release - filter to a specific release version
- Finding ID search - free-text search across finding IDs and aliases
- Show Suppressed toggle - include or exclude suppressed findings
- Show Unsuppressed toggle - include or exclude active findings
When component, branch, or release filters are active, the view also surfaces new findings from those release artifacts that have not yet been analyzed, allowing you to triage them inline.
Admin Settings
Organization admins can configure the following under Org Settings → Admin Settings.
Justification Mandatory
Enable Justification Mandatory to require users to select a justification when creating any finding analysis. When enabled, the justification field becomes required in the Create Analysis dialog.
Violation Ignore Patterns
Configure regex patterns to automatically exclude specific violations from all reports:
- License Violation Ignore Patterns - matched against license identifiers, refer to License Compliance for more details
- Security Violation Ignore Patterns - matched against security violation details
- Operational Violation Ignore Patterns - matched against operational violation details
Any violation matching a configured pattern is excluded organization-wide. Click Save Ignore Patterns to apply.

