> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/visual-studio-code-extension/view-analysis-results-from-visual-studio-code-extension/analysis-results-snyk-code.md).

# Analysis results: Snyk Code

How to view Snyk Code security results in the Visual Studio Code extension

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Analysis results: Snyk Code

Snyk Code analysis shows security vulnerabilities in your code with every scan.

### Snyk Code vulnerability window

<figure><img src="https://558411700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEEjSXQQu36y0vmFV8zf%2Fuploads%2Fgit-blob-683f536680ec9cce60b4102e71889a11c3f0d02f%2FScreenshot%202023-03-17%20at%2012.25.28.png?alt=media" alt="Snuk Code vulnerability window"><figcaption><p>Snyk Code vulnerability window</p></figcaption></figure>

The Snyk suggestion panel on the right of the results screen shows the Snyk Code Vulnerability name, the line it was found in, a suggestion for a fix, and an option to ignore, either in the entire file or a specific line.

On the **Problems** tab of the Visual Studio Code results screen, you can see all Code issues found in your Project.

<figure><img src="https://558411700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEEjSXQQu36y0vmFV8zf%2Fuploads%2Fgit-blob-77b42fcdda4e48345064e03dff6370bbd633d0a7%2FScreenshot%202023-03-17%20at%2013.41.55.png?alt=media" alt="Visual Studio Code Problems tab"><figcaption><p>Visual Studio Code Problems tab</p></figcaption></figure>

Snyk also includes a feedback mechanism to report false positives so others do not see the same issue (bottom left).

### Snyk Code editor window

The vulnerabilities are visible within the editor, with the detailed information available on hover.

<figure><img src="https://558411700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEEjSXQQu36y0vmFV8zf%2Fuploads%2Fgit-blob-788c25296dc9a128d61e440e89ef8ec1a6bb3910%2FScreenshot%202023-03-17%20at%2012.31.45.png?alt=media" alt="Snyk Code editor window"><figcaption><p>Snyk Code editor window</p></figcaption></figure>

Choose **Quick Fix** to open the details panel for an issue using Code Action.

You can also choose to ignore a suggestion, either a particular one or a recurring one in the current file, using **Quick Fix**.

<figure><img src="https://558411700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEEjSXQQu36y0vmFV8zf%2Fuploads%2Fgit-blob-6061fbe4f0596357c96c2a56b33e73b76501f5fc%2FScreenshot%202023-03-17%20at%2016.34.21.png?alt=media" alt="Quick Fix menu"><figcaption><p>Quick Fix menu</p></figcaption></figure>

<figure><img src="https://558411700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIEEjSXQQu36y0vmFV8zf%2Fuploads%2Fgit-blob-44a5c909570e6d4b5aee2d3f6421c6946d66a3e7%2FScreenshot%202023-03-17%20at%2012.32.22.png?alt=media" alt="Ignore options with issue detail"><figcaption><p>Ignore options with issue detail</p></figcaption></figure>


---

# 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.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/visual-studio-code-extension/view-analysis-results-from-visual-studio-code-extension/analysis-results-snyk-code.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.