Skip to main content
N
All NuGet guides

Practical workflow

Review NuGet licenses before shipping

License metadata is a useful first signal, not a legal conclusion. This workflow helps an engineering team identify what needs attention before a package enters a distributable product.

Open License Check

Workflow

  1. 1

    Use the same project input used for restore

    Select the .csproj or Directory.Packages.props file that declares the package versions you plan to ship.

  2. 2

    Separate known, copyleft and unknown entries

    Treat unknown SPDX metadata as a review queue. For copyleft entries, read the actual license and distribution obligations.

  3. 3

    Verify package-specific exceptions

    Open the package and license details for dual licenses, custom terms, embedded notices and changed licensing between versions.

  4. 4

    Document the release decision

    Record attribution, notice, source-offer and approval requirements with the version you selected.

What this workflow gives you

  • A reproducible inventory of detected license expressions across direct and transitive dependencies.
  • A smaller review set for unknown or reciprocal licenses.
  • Clear hand-off material for the person responsible for compliance decisions.

Choose packages with context

JSON libraries for .NETLogging packages for .NETTesting frameworks for .NET

Data, method and limits

Sources: the project file you select and the public NuGet v3 registry. Refresh: registry metadata is queried while the tool runs; your file stays in the browser. Method: the workflow turns declared versions and published package metadata into a review queue. Limit: License classification is based on published SPDX metadata and local rules. It cannot determine legal compatibility, contractual obligations or whether a package contains additional notices.