SdkCheck 0.5.0
dotnet add package SdkCheck --version 0.5.0
NuGet\Install-Package SdkCheck -Version 0.5.0
<PackageReference Include="SdkCheck" Version="0.5.0"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
<PackageVersion Include="SdkCheck" Version="0.5.0" />
<PackageReference Include="SdkCheck"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
paket add SdkCheck --version 0.5.0
#r "nuget: SdkCheck, 0.5.0"
#:package SdkCheck@0.5.0
#addin nuget:?package=SdkCheck&version=0.5.0
#tool nuget:?package=SdkCheck&version=0.5.0
SdkCheck
Warns at build time when the .NET SDK or runtime in use has published CVEs, or sits on a channel that has reached end of support.
A CVE in the .NET SDK or runtime is fixed in the next patch release. The SDK a build runs on is whatever was installed on the machine, baked into the CI image or pinned in global.json, and it picks the runtime the output is built against. A project keeps compiling, testing and shipping on a version with published CVEs until someone notices.
NuGetAudit covers NuGet packages. CheckSdkVulnerabilities covers the SDK, on .NET 11 and later. That leaves the runtime, where most .NET CVEs land, and every SDK before 11. The usual substitutes - dotnet sdk check, a global.json floor, a hand-written version baseline - never name a CVE.
SdkCheck compares the SDK and runtime actually in use against Microsoft's live release metadata, so a CVE published tomorrow is reported tomorrow with nothing to bump.
See https://github.com/SimonCropp/SdkCheck for full documentation.
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.