nuget-package-updater

To safely update NuGet package versions, scan and validate candidate updates against target frameworks and vulnerability metadata, preview safe changes, and generate a decision document before writing to Directory.Packages.props. Explicit locks and pins are preserved during the update process.

Yes, you can check for vulnerable NuGet dependencies locally by consulting NuGet VulnerabilityInfo APIs. The updater validates candidate versions against vulnerability metadata to avoid deprecated, unlisted, or compromised packages before applying any changes.

The best way to manage Directory.Packages.props updates safely is by validating candidate package versions against target frameworks via NuGet Registrations APIs, ensuring compatibility while enforcing lock rules and generating a decision document before writing changes.

Yes, the NuGet updater respects locked or pinned package versions. It locates and adjusts Version attributes while explicitly preserving Locked and Pin metadata in Directory.Packages.props to maintain your dependency management constraints.

You can generate documentation for NuGet package version changes by running the updater in check mode. This produces a deterministic Markdown decision document in the docs/pkgs-versions directory, describing all update decisions and safety validations before changes are applied.