Skip to main content
This section appears in the Vulnerability side panel → Vulnerability Details tab and is generated for each vulnerability independently.

​
What the Reasoning Includes

The reasoning provides a concise high-level summary of the vulnerability remediation analysis and outcome, including:
  • Upgrade Analysis per Affected Package
    Versions evaluated, selected upgrade path, and why the version was chosen.
  • Breaking Change Assessment
    Whether breaking changes were identified and how they impact remediation safety.
  • Verification and Testing Performed
    What validation steps were executed, such as build checks, dependency resolution, or tests, and why these checks were required.
  • Remediation Outcome and Root Cause (if Failed)
    If remediation failed, the reasoning explains the high-level root cause, such as dependency conflicts, incompatible code usage, or verification failures.

​
Vulnerabilities Without Available Remediation

If remediation cannot be completed, Backline provides a clear explanation of why remediation is not possible. Common reasons include:
  • No fixed version is available from the package maintainer
  • Upgrade failed due to dependency conflicts or incompatibility
  • The affected package or language is not currently supported
  • Required remediation steps cannot be safely automated
This ensures full transparency into remediation limitations and helps you understand the next recommended action.

​
When is the Reasoning Shown

The Vulnerability Reasoning is shown only when analysis has completed and reasoning is available. If analysis has not yet completed, this section will not be displayed.