Skip to content
| Marketplace
Sign in
Azure DevOps>Azure Pipelines>Dot Net List Package Check
Dot Net List Package Check

Dot Net List Package Check

Samayas

samayas.eu
|
5 installs
| (0) | Free
List all possible package vunlerabilities or depreciated or outdated.
Get it free

Overview

The .NET Core List Packages Check task validates NuGet packages in your .NET projects by running dotnet list package commands during your build pipeline. It helps identify security vulnerabilities, deprecated packages, and outdated dependencies before they reach production.

In a CI environment this task can be helpful to detect included NuGet packages that might pose an issue.

Depending on configuration this can block the build pipeline whether you choose it or not.

Prerequisites

This extension supports Azure DevOps Server 2019 and Azure DevOps Online.

Video

A comprehensive video demonstration of this extension is available at https://l.samayas.eu/g9r8vJrrxp

How to use

After installing the extension, add the .NET Core List Packages Check task to a new or existing build definition.

Once you've added the .NET Core List Packages Check you should have the following:

add-task

Once you've added the task to your Build pipeline you need to configure your individual task.

configure-task

Inside your task configuration you have 2 distinct blocks that are important:

  • The Scope Coverage determines what is scanned.
  • The Scan Type determines what type of scan is executed.

Scope Coverage

Under the Scope Coverage in essence you define on what the task is executed.

  • Solution scans the whole solution in the source folder of your pipeline.
  • Project scans only the specified project in your source folder of your pipeline.

When having selected the Project scope an extra field will be available to enter the specified project.

scopecoverage-project

The underlying command only supports solution or project and you can't have multiple projects scanned.

Scan Type

In the Scan Type you determine what type of scan is executed.

  • Vulnerabilities: Detects packages with known security vulnerabilities.
  • Deprecated: Finds packages that have been deprecated by their authors.
  • OutDated: Identifies packages with newer versions available.

Each of these scan types are distinct and if you need a multitude you need to add this task multiple times.

Enable Transitive Package Checks

  • When enabled (default), scans both direct and transitive (indirect) dependencies.
  • When disabled, only scans packages directly referenced in your project files

Scan Type Outdated

When the scan Type is outdated there are 3 new options.

  • All version: Scan for all different versions.
  • Highest Minor: Scan only for highest minor changes.
  • Highest Patch: Scan only for highest patch changes.

When Highest Minor or Highest patch is selected then Transitive scans wont be executed.

scantype-outdated

Build Behavior

The task affects your pipeline outcome based on what it finds:

  • Direct Issues Found : Build fails with an error message and references the log files.
  • Transitive Issues Found : Build succeeds with warnings (SucceedWithIssues status).
  • **No Issues Found: Build continues normally with a success message.
  • Unrestorable Projects Skipped : Projects that dotnet restore cannot restore (no NuGet assets file afterwards, e.g. WiX setup projects mapped only to custom solution build types, or old-style .wixproj/.sqlproj/.vcxproj formats) cannot be audited by dotnet list package. They are reported as a warning and do not affect the outcome; the remaining projects are scanned individually.

Advanced

The Advanced section contains configuration options for customizing the task's working directory behavior.​

Solution Directory Location

This parameter allows customization of the working directory where the task searches for the solution or project files. By default, the task uses $(Build.SourcesDirectory), which points to the root of the repository. This setting is useful when the solution file is not located in the root of the repository but instead resides in a subfolder. For example, if the solution is located in a src folder or a nested directory structure, this parameter can be adjusted to point to that specific location.

Default Value: $(Build.SourcesDirectory)

Usage Example: If the solution is located in a subfolder called /MyApplication, set this value to $(Build.SourcesDirectory)/MyApplication. ​

Output Artifacts

All scan results are saved to the pipeline workspace under nuget-audit:

Depending on whether the Transitive scan is enabled or not this task will generate 2 or 4 files as output

  • direct.log : Human-readable output for direct package scan
  • direct.json : JSON output for direct package scan
  • include-transitive.log : Human-readable output including transitive packages (when enabled)
  • include-transitive.json : JSON output including transitive packages (when enabled)

If you choose to afterwards this can be added as an artifact on the build.

Target

The goal of this add-in is to detect potential issues with included Nuget packages.

Version History

Version 1.1 Solutions containing projects that dotnet restore cannot restore (no NuGet assets file afterwards, e.g. WiX setup projects mapped only to custom solution build types, or old-style project formats) no longer fail the scan. These projects are detected up front, reported as warnings, and the remaining projects are scanned individually. Version 1.0 Initial Version

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft