NuGet Upgrade Dependency Diff

Compare declared dependency groups between two exact versions of a public NuGet.org package. Get structured additions, removals and dependency-range changes for upgrade reviews without manually joining metadata exports.

Quick start

{"packageId":"Newtonsoft.Json","fromVersion":"12.0.3","toVersion":"13.0.3"}

One package and version pair per run. Versions must match the source normalized three/four-part spelling. Prereleases supported; floating versions and build metadata unsupported.

Output

One dataset row contains packageId, fromVersion, toVersion, status (CHANGED/UNCHANGED), changeCount, before, after, changes, sourceUrl, checkedAt and scope. Before/after hold normalized groups with framework and dependencies (id/range). Empty framework means all frameworks.

Changes: GROUP_ADDED, GROUP_REMOVED, DEPENDENCY_ADDED, DEPENDENCY_REMOVED, RANGE_CHANGED. Added/removed groups include complete dependencies and count once, without counting children separately. Empty groups are preserved. Ranges compare declaration text, not mathematical equivalence. IDs are case-normalized; framework labels are exact source strings.

Use cases

Attach evidence to dependency upgrade reviews; identify new direct dependencies or dropped declared framework groups; export JSON or CSV via Apify. JSON preserves the complete nested before/after data.

Limits

This is a declaration comparison, not a compatibility or security verdict. It does not resolve transitive dependencies, select compatible frameworks, inspect DLLs, download packages, compare APIs or prove an application will build. Dependency groups are not a complete list of supported frameworks. Test upgrades in your build pipeline. No private feed, authentication or proxy support.

Only NuGet.org HTTPS metadata is requested. The SemVer2 registration endpoint is discovered dynamically. Maximum eight registration pages, ten requests, 4 MiB decoded per response, 8 MiB total, and ten seconds per request. Oversized/incomplete sources, unknown packages/versions and source failures fail before comparison delivery. No state is maintained between runs.

Pricing

$0.01 per successful comparison, including unchanged/same-version comparisons. No startup or per-change fee. Platform usage included. Source/validation failures emit no comparison event. Reruns are separate comparisons and may be charged again; storage and billing are not an exactly-once transaction.

Source and support

Uses the official NuGet metadata API. Unaffiliated with NuGet or Microsoft. Open an Apify Issue with package ID, exact versions and run ID for reproducible problems. Never include credentials.