Ecosystem · .NET · NuGet

Vulnerabilities in your NuGet packages, and in your .NET version.

LibWatch reads your project files, central package management and NuGet lockfiles, and tracks the end of life of the target framework and the SDK.

Read with an AI .md version

What LibWatch reads in the repository

  • *.csproj · *.fsproj
  • Directory.Packages.props
  • packages.lock.json
  • nuget.config (private registries)

Language version: TargetFramework and SDK

Nothing else: no cloning, no code run.

What LibWatch checks

The packages, and the .NET version

NuGet packages

Known vulnerabilities

Every package in the lockfile checked against OSV, which includes GitHub advisories.

.NET version

End of life

The declared version is tracked: you know when it stops getting fixes.

Health

License policy

Licenses that conflict with your project's policy are flagged.

An alert, in practice

A NuGet vulnerability, with the version that fixes it

The vulnerabilities that affect your versions, with the fixed version. Nothing more.

Real severity

CVSS severity and presence in the CISA KEV catalog

What to do

The fixed version, and the affected project

Where

Email, Slack, Zulip or webhook, set per project

hr-portal · ASP.NET

Example · analysis from October 22

  • .NET (target)

    net8.0

    Ends November 10, 2026
  • System.Text.Json

    8.0.4

    High severity
  • Serilog

    4.0.1

    Up to date

Rechecked every night at 2 a.m.

End of life

Where your .NET version stands

Official Microsoft schedule, checked on October 22, 2026.

Version Type End of life Action
.NET 10 LTS → November 2028 Recommended version
.NET 9 STS November 10, 2026 Upgrade to .NET 10
.NET 8 LTS November 10, 2026 Upgrade to .NET 10

Dates checked on October 22, 2026.

Get started

Your first report in a few minutes

No pipeline to change.

Connect GitHub or GitLab

Self-hosted GitLab instances included.

Choose your .NET repositories

LibWatch finds the files listed above on its own, even in a monorepo.

Read the report, set up alerts

Exploited vulnerabilities first, fixed versions, language end of life.

Frequently asked questions

LibWatch and .NET

Do I need to install anything in the project?

No. LibWatch reads dependency files through the GitHub or GitLab API, without adding anything to your pipeline.

Are private registries supported?

Yes. A package from a private registry is identified as such: its name is never sent to a third-party service, and it stays in the project's inventory.

Does LibWatch detect the version installed on the server?

No. LibWatch reads the version declared in the repository (version file, lockfile or manifest). It has no access to your servers.

Your .NET projects, checked tonight.

Hosted in France by OVHcloud