LazyNuGet 1.0.4

LazyNuGet

<div align="center"> <img src=".github/logo.svg" alt="LazyNuGet Logo" width="600"> </div>

<div align="center">

</div>

A terminal-based NuGet package manager inspired by lazygit.

<div align="center">

⭐ If you find LazyNuGet useful, please consider giving it a star! ⭐

It helps others discover the project and motivates continued development.

</div>

LazyNuGet brings a fast, keyboard-driven interface to NuGet package management. Navigate your projects, view package details, check for updates, and search NuGet.org—all without leaving the terminal.

Browse. Update. Search.

View more screenshots

Quick Start

Get LazyNuGet running in seconds:

Option 1: .NET Global Tool (if you have .NET 9 installed)

dotnet tool install --global LazyNuGet
lazynuget

Option 2: Self-contained binary (no .NET required)

curl -fsSL https://raw.githubusercontent.com/nickprotop/lazynuget/main/install.sh | bash
lazynuget

That's it! Use arrow keys (or the mouse) to navigate, Enter to view package details, and Ctrl+S to search NuGet.org.

Features

Input

LazyNuGet is fully usable with both keyboard and mouse. Click to focus controls, scroll lists, and activate buttons. Keyboard shortcuts are available for every action and are the fastest way to navigate.

Keyboard Shortcuts

Installation

.NET Global Tool (Recommended for .NET developers)

If you have .NET 10.0 or later installed:

dotnet tool install --global LazyNuGet

Advantages:

• ✅ Single command installation
• ✅ Automatic updates with dotnet tool update -g LazyNuGet
• ✅ Works on all platforms (Windows, macOS, Linux)
• ✅ Lightweight (~5MB vs ~60MB for self-contained)

Update:

dotnet tool update --global LazyNuGet

Uninstall:

dotnet tool uninstall --global LazyNuGet

Self-Contained Binaries (No .NET required)

Linux

Download and install the latest release:

curl -fsSL https://raw.githubusercontent.com/nickprotop/lazynuget/main/install.sh | bash

This automatically:

• Downloads the binary for your architecture (x64 or ARM64)
• Installs to ~/.local/bin/lazynuget
• Adds ~/.local/bin to your PATH

After installation, reload your shell:

source ~/.bashrc  # or ~/.zshrc

macOS

curl -fsSL https://raw.githubusercontent.com/nickprotop/lazynuget/main/install.sh | bash

The installer detects macOS automatically and:

• Downloads the correct binary (Intel or Apple Silicon)
• Installs to /usr/local/bin/ (or ~/.local/bin/ if not writable)
• Clears the Gatekeeper quarantine flag

Note: If macOS still blocks the binary, run: xattr -d com.apple.quarantine $(which lazynuget)

Windows

Open PowerShell and run:

irm https://raw.githubusercontent.com/nickprotop/lazynuget/main/install.ps1 | iex

This installs to %LOCALAPPDATA%\Programs\LazyNuGet\ and adds it to your user PATH.

Note: If Windows SmartScreen blocks the binary, click "More info" then "Run anyway".

Manual Install

Download the latest binary for your platform:

• lazynuget-linux-x64 (Linux Intel/AMD)
• lazynuget-linux-arm64 (Linux ARM)
• lazynuget-osx-x64 (macOS Intel)
• lazynuget-osx-arm64 (macOS Apple Silicon)
• lazynuget-win-x64.exe (Windows Intel/AMD)
• lazynuget-win-arm64.exe (Windows ARM)

Linux/macOS — make executable and move to PATH:

chmod +x lazynuget-linux-x64
sudo mv lazynuget-linux-x64 /usr/local/bin/lazynuget

Build from Source

Requirements:

• .NET 10.0 SDK
• Terminal with Unicode support

git clone https://github.com/nickprotop/lazynuget.git
cd lazynuget
dotnet build -c Release

Run with:

dotnet run [path]

Usage

# Manage packages in current directory
lazynuget

# Manage packages in specific directory
lazynuget /path/to/your/projects

# Migrate all packages.config projects in a directory tree (headless, no UI)
lazynuget --migrate /path/to/your/projects

# Migrate all projects to Central Package Management (headless)
lazynuget --migrate-cpm /path/to/your/projects

# Show help
lazynuget --help

LazyNuGet will scan the directory for .csproj files and display all discovered projects and their packages.

Troubleshooting

Projects not found

LazyNuGet scans for .csproj files. Make sure you open the folder that contains your projects (or a parent folder). Folders named bin, obj, .git, and node_modules are skipped automatically.

Packages show as up-to-date but shouldn't be

LazyNuGet caches package metadata during a session. Press Ctrl+R to force a full reload and clear the cache. Also confirm you have network access to NuGet.org.

Outdated/vulnerable badges not appearing

Version checks run in the background after projects load. If the badge never appears, check that NuGet.org is reachable. A red indicator in the status bar usually means a source failed to connect.

Private feed not showing packages

1. Confirm the feed URL is correct — open Ctrl+P → Sources tab and verify it is enabled.
2. If the feed requires authentication, make sure credentials are saved (edit the source and re-enter them).
3. On Linux/macOS credentials are stored as clear-text in ~/.nuget/NuGet/NuGet.Config. On Windows they are encrypted with DPAPI.
4. If the feed was added outside LazyNuGet (e.g. via dotnet nuget add source), it will appear automatically — LazyNuGet reads the standard NuGet.config hierarchy.

Authentication errors on a private feed

Re-enter credentials via Ctrl+P → select the source → press E to edit. If the feed uses a PAT (Personal Access Token), put the token in the Password field (username can be anything, e.g. pat).

Project shows zero packages (legacy packages.config project)

LazyNuGet reads <PackageReference> elements by default. Older .NET Framework projects use a separate packages.config file instead, which is also supported — they appear in the project list with a legacy badge and their packages are shown read-only.

To manage these projects fully, migrate them to the modern PackageReference format:

• In-app: navigate into the project's packages view and press Ctrl+M. LazyNuGet will confirm, create a .csproj.bak backup, convert all packages.config entries to <PackageReference> elements, remove old NuGet <Reference> hint-paths, and delete packages.config. After migration the project reloads as a normal project.
• Headless (batch): run lazynuget --migrate /path/to/solution to migrate every packages.config project in the tree at once. Results are printed to stdout and a .csproj.bak backup is created next to each migrated file. If a migration fails for any reason the original .csproj is restored from the backup automatically.

Framework assembly references (System, System.Core, etc.) are never touched — only NuGet hint-path references are removed.

Terminal display looks broken (missing borders, garbled text)

LazyNuGet requires a terminal with Unicode and 256-colour support. Recommended terminals: Windows Terminal, iTerm2, GNOME Terminal, Alacritty, Kitty. The basic Windows cmd.exe console is not supported — use Windows Terminal instead.

macOS: "cannot be opened because the developer cannot be verified"

Run: xattr -d com.apple.quarantine $(which lazynuget)

Uninstall

Linux / macOS

lazynuget-uninstall

Or manually:

curl -fsSL https://raw.githubusercontent.com/nickprotop/lazynuget/main/uninstall.sh | bash

Windows

irm https://raw.githubusercontent.com/nickprotop/lazynuget/main/uninstall.ps1 | iex

Settings are stored in ~/.config/LazyNuGet/ (Linux), ~/Library/Application Support/LazyNuGet/ (macOS), or %APPDATA%\LazyNuGet\ (Windows) and are not removed by the uninstaller.

Built With

• SharpConsoleUI - A .NET library for building terminal user interfaces with responsive layouts and window management

Author

Nikolaos Protopapas

• GitHub: @nickprotop

License

This project is licensed under the MIT License - see the LICENSE file for details.