Dotnet outdated
A .NET Core global tool to display and update outdated NuGet packages in .NET projects from the command line.
What is Dotnet outdated?
dotnet-outdated is a .NET Core global command-line tool that identifies and updates outdated NuGet packages in .NET projects. It solves the problem of managing dependencies outside of an IDE, providing developers with a way to keep their projects current directly from the terminal. The tool offers detailed reporting, automated upgrades, and integration into CI/CD pipelines.
.NET developers and teams working in command-line or CI/CD environments who need to manage NuGet package dependencies without relying on Visual Studio's GUI.
Developers choose dotnet-outdated because it provides a dedicated, feature-rich CLI tool for NuGet dependency management that is not natively included in the .NET Core SDK, offering greater control, automation capabilities, and integration into modern development workflows than manual methods.
Overview
A .NET Core global tool to display and update outdated NuGet packages in a project
Use Cases
Best For
- Checking for outdated NuGet packages in a .NET solution from the command line
- Automating package updates within CI/CD pipelines
- Analyzing transitive dependencies for security or compliance audits
- Generating reports on dependency health in JSON, CSV, or Markdown formats
- Integrating package management workflows with AI agents via its MCP server
- Managing dependencies in headless or server-based development environments
Not Ideal For
- Teams that exclusively rely on Visual Studio's GUI for package management and avoid command-line interactions
- Projects in polyglot environments requiring unified dependency management across ecosystems like npm, pip, or Maven
- Organizations with strict change control policies that prohibit automated updates without extensive manual review
Pros & Cons
Pros
Supports both automatic and interactive package updates via the -u option, allowing teams to choose between hands-off and controlled upgrade processes directly from the CLI.
Configurable transitive dependency reporting with -t and -td options provides insights into indirect package health, crucial for security audits and compliance checks.
Can return a non-zero exit code with the -f flag when updates are found, enabling easy failure in build pipelines for automated dependency compliance.
Includes a built-in MCP server for integration with AI assistants like Claude Desktop, as highlighted in the README, future-proofing the tool for emerging workflows.
Cons
README specifically notes issues on macOS with user-level config file detection and the need for clear-text password storage, complicating secure feed setup on non-Windows systems.
FAQ acknowledges that using the upgrade option can cause unrelated changes to .csproj files due to reliance on the underlying dotnet add package command, risking unexpected edits.
Documentation warns that analyzing transitive dependencies too deeply with -td can significantly slow down the process, making it impractical for large, complex dependency graphs.
Frequently Asked Questions
Related Projects
AutoMapperA convention-based object-object mapper in .NET.
HumanizerHumanizer meets all your .NET needs for manipulating and displaying strings, enums, dates, times, timespans, numbers and quantities
AngleSharp:angel: The ultimate angle brackets parser library parsing HTML5, MathML, SVG and CSS to construct a DOM based on the official W3C specifications.
markdigA fast, powerful, CommonMark compliant, extensible Markdown processor for .NET
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.