Dependency risks

How to fix view and manage dependency risks in SonarQube for Visual Studio.

In connected mode, you can see the results from SonarQube Server’s Advanced security tools for Software composition analysis (SCA), directly in the Visual Studio UI. This includes:

• vulnerabilities in your third-party open source dependencies.

• seeing where your open source dependencies may be in conflict with your organization’s license policies.

Prerequisites

• Using SonarQube Server Enterprise edition, version 2025.4 or later.

• Having the Advanced Security add-on with Software Composition Analysis (SCA) enabled on your SonarQube Server instance.

• Running SonarQube for Visual Studio in connected mode with SonarQube Server. See the pages on Connected mode and Connected mode setup for more details.

How to view your dependency risks

To see dependency risks in SonarQube for Visual Studio, go to Extensions > SonarQube > Connected Mode > View Dependency risks. The list of dependency risks is displayed in the SonarQube Dependency Risks tool window.

For each dependency risk, the following information is displayed:

• Risk type: Vulnerability and Prohibited license

• Risk severity: Blocker, High, Medium, Low, or Info

• Package name

• Package version

You can select a risk to open it in SonarQube Server to get more details.

Fixing dependency risks

Because dependency risk analysis requires that you run in connected mode, any changes you make to the code must be analyzed by your instance of SonarQube Server.

Here are two options to resolve dependency risks displayed by SonarQube for Visual Studio:

• After you fix the dependency risk in your IDE, commit your code to the server and trigger a new analysis on SonarQube Server. The new status of the risk will be reflected in your IDE.

• Mark the dependency risk as Confirmed, Accepted, or Safe directly from SonarQube for Visual Studio UI or in SonarQube Server. You can also add comments. The status update is then reflected in Visual Studio and SonarQube Server.