Azure.Identity 1.13.0-beta.2

Prefix Reserved
This is a prerelease version of Azure.Identity.
dotnet add package Azure.Identity --version 1.13.0-beta.2                
NuGet\Install-Package Azure.Identity -Version 1.13.0-beta.2                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Azure.Identity" Version="1.13.0-beta.2" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Azure.Identity --version 1.13.0-beta.2                
#r "nuget: Azure.Identity, 1.13.0-beta.2"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Azure.Identity as a Cake Addin
#addin nuget:?package=Azure.Identity&version=1.13.0-beta.2&prerelease

// Install Azure.Identity as a Cake Tool
#tool nuget:?package=Azure.Identity&version=1.13.0-beta.2&prerelease                

Azure Identity client library for .NET

The Azure Identity library provides Microsoft Entra ID (formerly Azure Active Directory) token authentication support across the Azure SDK. It provides a set of TokenCredential implementations that can be used to construct Azure SDK clients that support Microsoft Entra token authentication.

Source code | Package (NuGet) | API reference documentation | Microsoft Entra ID documentation

Getting started

Install the package

Install the Azure Identity client library for .NET with NuGet:

dotnet add package Azure.Identity

Prerequisites

  • An Azure subscription.
  • The Azure CLI can also be useful for authenticating in a development environment, creating accounts, and managing account roles.

Authenticate the client

When debugging and executing code locally, it's typical for a developer to use their own account for authenticating calls to Azure services. There are several developer tools that can be used to perform this authentication in your development environment.

Authenticate via Visual Studio

Developers using Visual Studio 2017 or later can authenticate a Microsoft Entra account through the IDE. Apps using DefaultAzureCredential or VisualStudioCredential can then use this account to authenticate calls in their app when running locally.

To authenticate in Visual Studio, select the Tools > Options menu to launch the Options dialog. Then navigate to the Azure Service Authentication options to sign in with your Microsoft Entra account.

Visual Studio Account Selection

Authenticate via Visual Studio Code

Developers using Visual Studio Code can use the Azure Account extension to authenticate via the editor. Apps using DefaultAzureCredential or VisualStudioCodeCredential can then use this account to authenticate calls in their app when running locally.

It's a known issue that VisualStudioCodeCredential doesn't work with Azure Account extension versions newer than 0.9.11. A long-term fix to this problem is in progress. In the meantime, authenticate via the Azure CLI.

Authenticate via the Azure CLI

Developers coding outside of an IDE can also use the Azure CLI to authenticate. Apps using DefaultAzureCredential or AzureCliCredential can then use this account to authenticate calls in their app when running locally.

To authenticate with the Azure CLI, run the command az login. For users running on a system with a default web browser, the Azure CLI launches the browser to authenticate the user.

Azure CLI Account Sign In

For systems without a default web browser, the az login command uses the device code authentication flow. The user can also force the Azure CLI to use the device code flow rather than launching a browser by specifying the --use-device-code argument.

Azure CLI Account Device Code Sign In

Authenticate via the Azure Developer CLI

Developers coding outside of an IDE can also use the Azure Developer CLI to authenticate. Apps using DefaultAzureCredential or AzureDeveloperCliCredential can then use this account to authenticate calls in their app when running locally.

To authenticate with the Azure Developer CLI, run the command azd auth login. For users running on a system with a default web browser, the Azure Developer CLI launches the browser to authenticate the user. For systems without a default web browser, the azd auth login --use-device-code command uses the device code authentication flow.

Authenticate via Azure PowerShell

Developers coding outside of an IDE can also use Azure PowerShell to authenticate. Apps using DefaultAzureCredential or AzurePowerShellCredential can then use this account to authenticate calls in their app when running locally.

To authenticate with Azure PowerShell, run the command Connect-AzAccount. For users running on a system with a default web browser and version 5.0.0 or later of Azure PowerShell, it launches the browser to authenticate the user. For systems without a default web browser, the Connect-AzAccount command uses the device code authentication flow. The user can also force Azure PowerShell to use the device code flow rather than launching a browser by specifying the UseDeviceAuthentication argument.

Key concepts

Credentials

A credential is a class that contains or can obtain the data needed for a service client to authenticate requests. Service clients across the Azure SDK accept credentials when they're constructed. Service clients use those credentials to authenticate requests to the service.

The Azure Identity library focuses on OAuth authentication with Microsoft Entra ID. It offers numerous credentials capable of acquiring a Microsoft Entra token to authenticate service requests. Each credential in this library is an implementation of the TokenCredential abstract class in Azure.Core, and any of them can be used to construct service clients capable of authenticating with a TokenCredential.

See Credential classes for a complete listing of available credential types.

DefaultAzureCredential

DefaultAzureCredential simplifies authentication while developing apps that deploy to Azure by combining credentials used in Azure hosting environments with credentials used in local development. For more information, see DefaultAzureCredential overview.

Continuation policy

As of version 1.10.1, DefaultAzureCredential attempts to authenticate with all developer tool credentials until one succeeds, regardless of any errors previous developer tool credentials experienced. For example, a developer tool credential may attempt to get a token and fail, so DefaultAzureCredential will continue to the next credential in the flow. Deployed service credentials stop the flow with a thrown exception if they're able to attempt token retrieval but don't receive one. Prior to version 1.10.1, developer tool credentials would similarly stop the authentication flow if token retrieval failed.

This behavior allows for trying all of the developer tool credentials on your machine while having predictable deployed behavior.

Examples

Authenticate with DefaultAzureCredential

This example demonstrates authenticating SecretClient from the Azure.Security.KeyVault.Secrets client library with DefaultAzureCredential:

// Create a secret client using the DefaultAzureCredential
var client = new SecretClient(new Uri("https://myvault.vault.azure.net/"), new DefaultAzureCredential());

Specify a user-assigned managed identity with DefaultAzureCredential

Many Azure hosts allow the assignment of a user-assigned managed identity. The following examples demonstrate configuring DefaultAzureCredential to authenticate a user-assigned managed identity when deployed to an Azure host. The sample code uses the credential to authenticate a BlobClient from the Azure.Storage.Blobs client library. It also demonstrates how you can specify a user-assigned managed identity either by a client ID or a resource ID.

Client ID

To use a client ID, take one of the following approaches:

  1. Set the DefaultAzureCredentialOptions.ManagedIdentityClientId property. For example:
// When deployed to an Azure host, DefaultAzureCredential will authenticate the specified user-assigned managed identity.

string userAssignedClientId = "<your managed identity client ID>";
var credential = new DefaultAzureCredential(
    new DefaultAzureCredentialOptions
    {
        ManagedIdentityClientId = userAssignedClientId
    });

var blobClient = new BlobClient(
    new Uri("https://myaccount.blob.core.windows.net/mycontainer/myblob"),
    credential);
  1. Set the AZURE_CLIENT_ID environment variable.
Resource ID

To use a resource ID, set the DefaultAzureCredentialOptions.ManagedIdentityResourceId property. The resource ID takes the form /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{identityName}. Because resource IDs can be built by convention, they can be more convenient when there are a large number of user-assigned managed identities in your environment. For example:

string userAssignedResourceId = "<your managed identity resource ID>";
var credential = new DefaultAzureCredential(
    new DefaultAzureCredentialOptions
    {
        ManagedIdentityResourceId = new ResourceIdentifier(userAssignedResourceId)
    });

var blobClient = new BlobClient(
    new Uri("https://myaccount.blob.core.windows.net/mycontainer/myblob"),
    credential);

Define a custom authentication flow with ChainedTokenCredential

While DefaultAzureCredential is generally the quickest way to authenticate apps for Azure, you can create a customized chain of credentials to be considered. ChainedTokenCredential enables users to combine multiple credential instances to define a customized chain of credentials. For more information, see ChainedTokenCredential overview.

Managed identity support

Managed identity authentication is supported either indirectly via DefaultAzureCredential or directly via ManagedIdentityCredential for the following Azure services:

As of version 1.8.0, ManagedIdentityCredential supports token caching.

Examples

These examples demonstrate authenticating SecretClient from the Azure.Security.KeyVault.Secrets client library with ManagedIdentityCredential.

Authenticate with a user-assigned managed identity

To authenticate with a user-assigned managed identity, you must specify one of the following IDs for the managed identity.

Client ID

string userAssignedClientId = "some client ID";

var credential = new ManagedIdentityCredential(
    ManagedIdentityId.FromUserAssignedClientId(userAssignedClientId));
var client = new SecretClient(new Uri("https://myvault.vault.azure.net/"), credential);

Resource ID

ResourceIdentifier userAssignedResourceId = new ResourceIdentifier(
    "/subscriptions/<subscriptionID>/resourcegroups/<resource group>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<MI name>");

var credential = new ManagedIdentityCredential(
    ManagedIdentityId.FromUserAssignedResourceId(userAssignedResourceId));
var client = new SecretClient(new Uri("https://myvault.vault.azure.net/"), credential);

Object ID

string userAssignedObjectId = "some object ID";

var credential = new ManagedIdentityCredential(
    ManagedIdentityId.FromUserAssignedObjectId(userAssignedObjectId));
var client = new SecretClient(new Uri("https://myvault.vault.azure.net/"), credential);
Authenticate with a system-assigned managed identity
var credential = new ManagedIdentityCredential(ManagedIdentityId.SystemAssigned);
var client = new SecretClient(new Uri("https://myvault.vault.azure.net/"), credential);

Sovereign cloud configuration

By default, credentials authenticate to the Microsoft Entra endpoint for the Azure Public Cloud. To access resources in other clouds, such as Azure US Government or a private cloud, use one of the following solutions:

  1. Configure credentials with the AuthorityHost property. For example:
var credential = new DefaultAzureCredential(
    new DefaultAzureCredentialOptions
    {
        AuthorityHost = AzureAuthorityHosts.AzureGovernment
    });

AzureAuthorityHosts defines authorities for well-known clouds.

  1. Set the AZURE_AUTHORITY_HOST environment variable to the appropriate authority host URL. For example, https://login.microsoftonline.us/. Note that this setting affects all credentials in the environment. Use the previous solution to set the authority host on a specific credential.

Not all credentials require this configuration. Credentials that authenticate through a developer tool, such as AzureCliCredential, use that tool's configuration.

Credential classes

Credential chains

Credential Usage Reference
DefaultAzureCredential Provides a simplified authentication experience to quickly start developing apps run in Azure. DefaultAzureCredential overview
ChainedTokenCredential Allows users to define custom authentication flows comprised of multiple credentials. ChainedTokenCredential overview

Authenticate Azure-hosted apps

Credential Usage
EnvironmentCredential Authenticates a service principal or user via credential information specified in environment variables.
ManagedIdentityCredential Authenticates the managed identity of an Azure resource.
WorkloadIdentityCredential Supports Microsoft Entra Workload ID on Kubernetes.

Authenticate service principals

Credential Usage Reference
AzurePipelinesCredential Supports Microsoft Entra Workload ID on Azure Pipelines. example
ClientAssertionCredential Authenticates a service principal using a signed client assertion.
ClientCertificateCredential Authenticates a service principal using a certificate. Service principal authentication
ClientSecretCredential Authenticates a service principal using a secret. Service principal authentication

Authenticate users

Credential Usage Reference
AuthorizationCodeCredential Authenticates a user with a previously obtained authorization code. OAuth2 authentication code
DeviceCodeCredential Interactively authenticates a user on devices with limited UI. Device code authentication
InteractiveBrowserCredential Interactively authenticates a user with the default system browser. OAuth2 authentication code
OnBehalfOfCredential Propagates the delegated user identity and permissions through the request chain. On-behalf-of authentication
UsernamePasswordCredential Authenticates a user with a username and password. Username + password authentication

Authenticate via development tools

Credential Usage Reference
AzureCliCredential Authenticates in a development environment with the Azure CLI. Azure CLI authentication
AzureDeveloperCliCredential Authenticates in a development environment with the Azure Developer CLI. Azure Developer CLI Reference
AzurePowerShellCredential Authenticates in a development environment with the Azure PowerShell. Azure PowerShell authentication
VisualStudioCredential Authenticates in a development environment with Visual Studio. Visual Studio configuration
VisualStudioCodeCredential Authenticates as the user signed in to the Visual Studio Code Azure Account extension. VS Code Azure Account extension

Note: All credential implementations in the Azure Identity library are threadsafe, and a single credential instance can be used by multiple service clients.

Environment variables

DefaultAzureCredential and EnvironmentCredential can be configured with environment variables. Each type of authentication requires values for specific variables.

Service principal with secret

Variable name Value
AZURE_CLIENT_ID ID of a Microsoft Entra application
AZURE_TENANT_ID ID of the application's Microsoft Entra tenant
AZURE_CLIENT_SECRET one of the application's client secrets

Service principal with certificate

Variable name Value
AZURE_CLIENT_ID ID of a Microsoft Entra application
AZURE_TENANT_ID ID of the application's Microsoft Entra tenant
AZURE_CLIENT_CERTIFICATE_PATH path to a PFX or PEM-encoded certificate file including private key
AZURE_CLIENT_CERTIFICATE_PASSWORD (optional) the password protecting the certificate file (currently only supported for PFX (PKCS12) certificates)
AZURE_CLIENT_SEND_CERTIFICATE_CHAIN (optional) send certificate chain in x5c header to support subject name / issuer based authentication

Username and password

Variable name Value
AZURE_CLIENT_ID ID of a Microsoft Entra application
AZURE_TENANT_ID ID of the application's Microsoft Entra tenant
AZURE_USERNAME a username (usually an email address)
AZURE_PASSWORD that user's password

Managed identity (DefaultAzureCredential)

Variable name Value
AZURE_CLIENT_ID The client ID for the user-assigned managed identity. If defined, used as the default value for ManagedIdentityClientId in DefaultAzureCredentialOptions

Configuration is attempted in the order in which these environment variables are listed. For example, if values for a client secret and certificate are both present, the client secret is used.

Continuous Access Evaluation

As of version 1.10.0, accessing resources protected by Continuous Access Evaluation (CAE) is possible on a per-request basis. This behavior can be enabled by setting the IsCaeEnabled property of TokenRequestContext via its constructor. CAE isn't supported for developer and managed identity credentials.

Token caching

Token caching is a feature provided by the Azure Identity library. The feature allows apps to:

  • Cache tokens in memory (default) or on disk (opt-in).
  • Improve resilience and performance.
  • Reduce the number of requests made to Microsoft Entra ID to obtain access tokens.

The Azure Identity library offers both in-memory and persistent disk caching. For more information, see the token caching documentation.

Brokered authentication

An authentication broker is an app that runs on a user's machine and manages the authentication handshakes and token maintenance for connected accounts. Currently, only Windows is supported via Web Account Manager (WAM). To enable support, use the Azure.Identity.Broker package.

Troubleshooting

See the troubleshooting guide.

Error handling

Errors arising from authentication can be raised on any service client method that makes a request to the service. This is because the first time the token is requested from the credential is on the first call to the service. Any subsequent calls might need to refresh the token. To distinguish these failures from failures in the service client, Azure Identity classes raise the AuthenticationFailedException with details on the error source in the exception message and possibly the error message. Depending upon the app, these errors may or may not be recoverable.

using Azure.Identity;
using Azure.Security.KeyVault.Secrets;

// Create a secret client using the DefaultAzureCredential
var client = new SecretClient(new Uri("https://myvault.vault.azure.net/"), new DefaultAzureCredential());

try
{
    KeyVaultSecret secret = await client.GetSecretAsync("secret1");
}
catch (AuthenticationFailedException e)
{
    Console.WriteLine($"Authentication Failed. {e.Message}");
}

For more information on handling errors from failed requests to Microsoft Entra ID or managed identity endpoints, see the Microsoft Entra ID documentation on authorization error codes.

Logging

See Enable and configure logging.

Thread safety

We guarantee that all credential instance methods are thread-safe and independent of each other (guideline). This ensures that the recommendation of reusing credential instances is always safe, even across threads.

Additional concepts

Client options | Accessing the response | Diagnostics | Mocking | Client lifetime

Next steps

Client libraries supporting authentication with Azure Identity

Many of Azure.Core-dependent client libraries support authenticating with TokenCredential and therefore the Azure Identity library. To learn more, see the library-specific docs.

Known issues

This library doesn't currently support scenarios relating to the Azure AD B2C service.

Open issues for the Azure.Identity library can be found here.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You'll only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (934)

Showing the top 5 NuGet packages that depend on Azure.Identity:

Package Downloads
Microsoft.Data.SqlClient

The current data provider for SQL Server and Azure SQL databases. This has replaced System.Data.SqlClient. These classes provide access to SQL and encapsulate database-specific protocols, including tabular data stream (TDS). Commonly Used Types: Microsoft.Data.SqlClient.SqlConnection Microsoft.Data.SqlClient.SqlException Microsoft.Data.SqlClient.SqlParameter Microsoft.Data.SqlClient.SqlDataReader Microsoft.Data.SqlClient.SqlCommand Microsoft.Data.SqlClient.SqlTransaction Microsoft.Data.SqlClient.SqlParameterCollection Microsoft.Data.SqlClient.SqlClientFactory When using NuGet 3.x this package requires at least version 3.4.

Microsoft.Extensions.Azure

Azure Client SDK integration with Microsoft.Extensions libraries

Microsoft.Extensions.Caching.SqlServer

Distributed cache implementation of Microsoft.Extensions.Caching.Distributed.IDistributedCache using Microsoft SQL Server. This package was built from the source code at https://github.com/dotnet/aspnetcore/tree/c70204ae3c91d2b48fa6d9b92b62265f368421b4

Microsoft.Identity.Web.Certificate

This package brings certificate management for MSAL.NET.

WindowsAzure.ServiceBus

Please note, for Azure Service Bus, Azure Event Hubs and Azure Relay, newer packages Azure.Messaging.ServiceBus, Azure.Messaging.EventHubs and Microsoft.Azure.Relay are available as of November 2020, February 2020 and March 2017 respectively. While WindowsAzure.ServiceBus will continue to receive critical bug fixes, we strongly encourage you to upgrade. Read https://aka.ms/azsdk/blog/msging/intro for more details. It adds Microsoft.ServiceBus.dll along with related configuration files to your project. This library allows AMQP 1.0 to be used as one of the protocols for communication with Microsoft Azure Service Bus. For more information on Messaging features, please visit: http://azure.microsoft.com/en-us/documentation/services/service-bus/ For more information on Event Hub features, please visit: http://go.microsoft.com/fwlink/?LinkID=403957 Please note that this package requires at least .Net Framework 4.6.2.

GitHub repositories (169)

Showing the top 5 popular GitHub repositories that depend on Azure.Identity:

Repository Stars
microsoft/semantic-kernel
Integrate cutting-edge LLM technology quickly and easily into your apps
jasontaylordev/CleanArchitecture
Clean Architecture Solution Template for ASP.NET Core
dotnet/efcore
EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
dotnet/AspNetCore.Docs
Documentation for ASP.NET Core
dotnet-architecture/eShopOnWeb
Sample ASP.NET Core 8.0 reference application, powered by Microsoft, demonstrating a layered application architecture with monolithic deployment model. Download the eBook PDF from docs folder.
Version Downloads Last updated
1.13.0-beta.2 11,235 9/17/2024
1.13.0-beta.1 49,172 7/24/2024
1.12.1 495,288 9/26/2024
1.12.0 15,874,554 6/17/2024
1.12.0-beta.3 12,394 6/11/2024
1.12.0-beta.2 42,257 5/7/2024
1.12.0-beta.1 15,945 4/23/2024
1.11.4 15,502,142 6/10/2024
1.11.3 10,272,895 5/7/2024 1.11.3 has at least one vulnerability with moderate severity.
1.11.2 4,773,181 4/19/2024 1.11.2 has at least one vulnerability with moderate severity.
1.11.1 3,824,622 4/16/2024 1.11.1 has at least one vulnerability with moderate severity.
1.11.0 8,043,184 4/9/2024 1.11.0 has at least one vulnerability with moderate severity.
1.11.0-beta.1 58,446 2/6/2024 1.11.0-beta.1 has at least one vulnerability with moderate severity.
1.10.4 37,738,677 11/13/2023 1.10.4 has at least one vulnerability with moderate severity.
1.10.3 59,075,939 10/18/2023 1.10.3 has at least one vulnerability with moderate severity.
1.10.2 12,408,006 10/9/2023 1.10.2 has at least one vulnerability with moderate severity.
1.10.1 2,220,758 9/13/2023 1.10.1 has at least one vulnerability with high severity.
1.10.0 3,317,196 8/15/2023 1.10.0 has at least one vulnerability with high severity.
1.10.0-beta.1 16,599 7/17/2023 1.10.0-beta.1 has at least one vulnerability with high severity.
1.9.0 15,992,703 5/11/2023 1.9.0 has at least one vulnerability with high severity.
1.9.0-beta.3 45,129 4/12/2023 1.9.0-beta.3 has at least one vulnerability with high severity.
1.9.0-beta.2 119,313 2/22/2023 1.9.0-beta.2 has at least one vulnerability with high severity.
1.9.0-beta.1 306,749 10/13/2022 1.9.0-beta.1 has at least one vulnerability with high severity.
1.8.2 17,770,272 2/8/2023 1.8.2 has at least one vulnerability with high severity.
1.8.1 4,066,077 1/13/2023 1.8.1 has at least one vulnerability with high severity.
1.8.0 12,275,509 11/9/2022 1.8.0 has at least one vulnerability with high severity.
1.8.0-beta.1 5,540 10/13/2022 1.8.0-beta.1 has at least one vulnerability with high severity.
1.7.0 77,018,096 9/19/2022 1.7.0 has at least one vulnerability with high severity.
1.7.0-beta.1 71,208 8/10/2022 1.7.0-beta.1 has at least one vulnerability with high severity.
1.6.1 7,065,245 8/8/2022 1.6.1 has at least one vulnerability with high severity.
1.6.0 83,437,235 4/5/2022 1.6.0 has at least one vulnerability with high severity.
1.6.0-beta.1 55,118 2/11/2022 1.6.0-beta.1 has at least one vulnerability with high severity.
1.5.0 36,251,218 10/14/2021 1.5.0 has at least one vulnerability with high severity.
1.5.0-beta.4 56,608 9/8/2021 1.5.0-beta.4 has at least one vulnerability with high severity.
1.5.0-beta.3 154,039 8/11/2021 1.5.0-beta.3 has at least one vulnerability with high severity.
1.5.0-beta.2 37,007 7/12/2021 1.5.0-beta.2 has at least one vulnerability with high severity.
1.5.0-beta.1 27,251 6/8/2021 1.5.0-beta.1 has at least one vulnerability with high severity.
1.4.1 9,161,991 8/5/2021 1.4.1 has at least one vulnerability with high severity.
1.4.0 43,551,414 5/12/2021 1.4.0 has at least one vulnerability with high severity.
1.4.0-beta.5 155,473 4/6/2021 1.4.0-beta.5 has at least one vulnerability with high severity.
1.4.0-beta.4 35,933 3/9/2021 1.4.0-beta.4 has at least one vulnerability with high severity.
1.4.0-beta.3 136,222 2/10/2021 1.4.0-beta.3 has at least one vulnerability with high severity.
1.4.0-beta.2 22,719 1/30/2021 1.4.0-beta.2 has at least one vulnerability with high severity.
1.4.0-beta.1 126,255 10/16/2020 1.4.0-beta.1 has at least one vulnerability with high severity.
1.3.0 130,575,453 11/13/2020 1.3.0 has at least one vulnerability with high severity.
1.3.0-beta.2 3,494 10/8/2020 1.3.0-beta.2 has at least one vulnerability with high severity.
1.3.0-beta.1 40,902 9/11/2020 1.3.0-beta.1 has at least one vulnerability with high severity.
1.2.3 10,931,207 9/11/2020 1.2.3 has at least one vulnerability with high severity.
1.2.2 1,297,677 8/20/2020 1.2.2 has at least one vulnerability with high severity.
1.2.1 856,875 8/18/2020 1.2.1 has at least one vulnerability with high severity.
1.2.0-preview.6 19,438 7/23/2020 1.2.0-preview.6 has at least one vulnerability with high severity.
1.2.0-preview.5 16,649 7/8/2020 1.2.0-preview.5 has at least one vulnerability with high severity.
1.2.0-preview.4 70,879 6/10/2020 1.2.0-preview.4 has at least one vulnerability with high severity.
1.2.0-preview.3 125,729 5/5/2020 1.2.0-preview.3 has at least one vulnerability with high severity.
1.2.0-preview.2 46,833 4/6/2020 1.2.0-preview.2 has at least one vulnerability with high severity.
1.2.0-preview.1 72,086 3/10/2020 1.2.0-preview.1 has at least one vulnerability with high severity.
1.1.1 13,055,211 2/11/2020 1.1.1 has at least one vulnerability with high severity.
1.1.0 894,985 11/25/2019 1.1.0 has at least one vulnerability with high severity.
1.0.0 3,025,208 10/30/2019 1.0.0 has at least one vulnerability with high severity.
1.0.0-preview.5 10,800 10/7/2019 1.0.0-preview.5 has at least one vulnerability with high severity.
1.0.0-preview.4 3,577 9/10/2019 1.0.0-preview.4 has at least one vulnerability with high severity.
1.0.0-preview.3 5,463 8/6/2019 1.0.0-preview.3 has at least one vulnerability with high severity.
1.0.0-preview.2 3,577 7/2/2019 1.0.0-preview.2 has at least one vulnerability with high severity.
1.0.0-preview.1 982 6/28/2019 1.0.0-preview.1 has at least one vulnerability with high severity.