Search packagesSearch nuget.org, the public gallery for .NET packages, by name and description, or browse it by owner, by tag or by kind of package. Results come back most relevant first, with each package's newest version, download count, owners and licence. The starting point for 'what is there for X in .NET?'. No API key required.
Get a packageGet everything nuget.org publishes about a package: what it is, its current version, its licence, its owners, how many times it has been downloaded, when it first and last shipped, and whether its newest release is deprecated. The full metadata of that newest release comes back with it, so a lookup usually needs only this one step. No API key required.
List a package's versionsWalk a package's release history. Every version comes back with the date it shipped, how many times it has been downloaded, whether it is a pre-release, and whether it is deprecated or has a known security advisory. Narrow it to stable releases only or to a window of dates, and order it by version or by publication date. No API key required.
Get a package versionGet everything about one release: when it shipped, how large the package file is, its licence, its release notes, which frameworks it is built for, whether it is deprecated or has a known advisory, and the repository and exact commit it was built from. Leave the version blank for the newest stable release. No API key required.
List a version's dependenciesList what one release pulls in, grouped by the framework it is built for. A package targeting .NET 8 and .NET Standard 2.0 often needs different things on each. Every dependency comes with the versions that satisfy it, written both in NuGet's notation and in plain words. Narrow it to one framework to see exactly what a project would get. No API key required.
Get a package's READMERead the README a release ships, as the Markdown its author wrote: what the package is for, how to install it, and the code example on its nuget.org page. Long files are trimmed to a length you set, and a release published without one says so rather than failing. No API key required.
Check a package for vulnerabilitiesCheck a package against the security advisories nuget.org publishes. Give it the version you ship and it answers whether that exact version is affected, by what, how severe it is, and the lowest release that is not, rather than handing back a version range for somebody to read. Leave the version out to see every advisory the package has ever had. No API key required.
Check for a newer versionCompare the version you have against what nuget.org publishes now. Answers whether there is an update, whether it is a major, minor or patch step, how many releases and how many days behind you are, and whether the version you are on is deprecated or has a known security advisory, all in one step, with a sentence ready to send. This is the action for a scheduled dependency check. No API key required.
