# NuGet Upgrade Dependency Diff (`quietdatatools/nuget-upgrade-dependency-diff`) Actor

Compare framework dependency declarations between two exact NuGet package versions. Export added/removed groups, direct dependencies and version-range changes for upgrade reviews. No package downloads or compatibility claims.

- **URL**: https://apify.com/quietdatatools/nuget-upgrade-dependency-diff.md
- **Developed by:** [QuietDataTools](https://apify.com/quietdatatools) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 successful comparisons

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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

```json
{"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](https://learn.microsoft.com/en-us/nuget/api/registration-base-url-resource). Unaffiliated with NuGet or Microsoft. Open an Apify Issue with package ID, exact versions and run ID for reproducible problems. Never include credentials.

# Actor input Schema

## `packageId` (type: `string`):

One public NuGet.org package ID.

## `fromVersion` (type: `string`):

Exact normalized source version; prereleases allowed. No floating versions or build metadata.

## `toVersion` (type: `string`):

Exact destination version. Same-version comparison allowed.

## Actor input object example

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

# Actor output Schema

## `comparison` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "packageId": "Newtonsoft.Json",
    "fromVersion": "12.0.3",
    "toVersion": "13.0.3"
};

// Run the Actor and wait for it to finish
const run = await client.actor("quietdatatools/nuget-upgrade-dependency-diff").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "packageId": "Newtonsoft.Json",
    "fromVersion": "12.0.3",
    "toVersion": "13.0.3",
}

# Run the Actor and wait for it to finish
run = client.actor("quietdatatools/nuget-upgrade-dependency-diff").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "packageId": "Newtonsoft.Json",
  "fromVersion": "12.0.3",
  "toVersion": "13.0.3"
}' |
apify call quietdatatools/nuget-upgrade-dependency-diff --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quietdatatools/nuget-upgrade-dependency-diff"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/SAYCR966Iu1FrnHWW/builds/NVa0EUXWlTEHqG8WR/openapi.json