> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-for-visual-studio/using/dependency-risks.md).

# 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, Cloud) [Advanced Security](/sonarqube-cloud/advanced-security.md) 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 <a href="#prerequisites" id="prerequisites"></a>

* Using SonarQube Server Enterprise edition version 2025.4 or later, or SonarQube Cloud with the Enterprise Plan.
* Having the Advanced Security product with SCA enabled. SCA is enabled by default in SonarQube Cloud and must be manually activated in SonarQube Server.
* Running SonarQube for Visual Studio in connected mode with SonarQube (Server, Cloud). See the pages on [Connected mode](/sonarqube-for-visual-studio/connect-your-ide/connected-mode.md) and [Connected mode setup](/sonarqube-for-visual-studio/connect-your-ide/setup.md) for more details.

## How to view your dependency risks <a href="#how-to-view-your-dependency-risks" id="how-to-view-your-dependency-risks"></a>

To see dependency risks in SonarQube for Visual Studio, go to **Extensions** > **SonarQube** > **Connected Mode** > **View SonarQube Report**. The list of dependency risks is displayed in the **SonarQube Report** tool window, which also lists security hotspots and taint vulnerabilities.

Dependency risks can be filtered by severity and status, and you can choose to display the dependency risks found for the current document or the open documents.

Deselect the **Issues**, **Security Hotspots**, and **Taint Vulnerabilities** filters to isolate your **Dependency Risks**. Select the **Filter** icon to expose the option to choose severity and status.

<div align="left"><figure><img src="https://1613591589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5CSDwdOaYoOAGYNiRqgl%2Fuploads%2F1r7jmiuQIFaXrTQh4qMZ%2Fsq-visual-studio-show-only-dependency-risks.png?alt=media&amp;token=d8d9036a-c3d0-4a6c-b37d-fe0022680c1d" alt="Dependency risks in the SonarQube Report tool window." width="563"><figcaption></figcaption></figure></div>

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**

To get more details on a dependency risk, select it and open it in SonarQube Server or SonarQube Cloud to get more details.

## Fixing dependency risks <a href="#fixing-dependency-risks" id="fixing-dependency-risks"></a>

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 or SonarQube Cloud.

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 and trigger a new analysis on SonarQube Server or SonarQube Cloud. The new status of the risk will be reflected in your IDE.
* Mark the dependency risk as **Confirmed**, **Accepted**, or **Safe** directly from the Visual Studio UI or in SonarQube Server or SonarQube Cloud. You can also add comments. The status update is then reflected in Visual Studio and SonarQube (Server, Cloud). \\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-for-visual-studio/using/dependency-risks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.