Snyk offers security scanning to test your projects for vulnerabilities, both through your CLI and through different integrations from our UI.
The following describes how to use Snyk to scan your .NET projects:
Package managers/Features |
CLI support |
Git support |
License scanning |
Remediation |
Runtime monitoring |
|
---|---|---|---|---|---|---|
|
✔︎ |
✔︎ |
✔︎ |
|||
|
✔︎ |
|
✔︎ |
Nuget
Follow the same instructions as Snyk CLI tool for .NET projectsIn order to build the dependency tree, Snyk analyzes the paket.dependencies and paket.lock files.
This section describes the unique CLI options available when working with .NET-based projects.
Option |
Description |
---|---|
|
When monitoring a .NET project using NuGet, the |
|
This is the folder in which your dependencies are installed. If you’ve assigned a unique name to this folder, then Snyk can only find it if you enter a custom path. Use the absolute or relative path, including the name of the folder where your dependencies reside. |
|
Test all .NET projects included in the given |
|
Test an individual .NET project. |
.NET projects can be imported from any of the Git services we support.
Once imported, Snyk analyzes your projects based on their supported manifest files and then builds the dependency tree and displays it from our app, similar to the following:

From the Snyk UI, you can configure whether Snyk should scan your entire project, including the build dependencies, or if the build dependencies should be skipped.
-
Go to
and click for .NET- If checked, Snyk scans all development dependencies.