# NuGet Package File and Dependency Export (`jpmarketdata/nuget-package-file-dependency-export`) Actor

Export exact NuGet versions into complete file paths and byte sizes, framework dependencies and runtime asset inventories without downloading package archives.

- **URL**: https://apify.com/jpmarketdata/nuget-package-file-dependency-export.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 package inventory delivereds

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 Package File and Dependency Export

Get complete file paths, byte sizes, framework dependency groups and observed runtime assets for exact public NuGet package versions without downloading or unpacking .nupkg archives. Build and import tools can use this metadata to plan which package assets they need.

### Input

`packages`: 1–20 objects with `id` and exact normalized `version`, for example `{"id":"Newtonsoft.Json","version":"13.0.3"}`. Omitted input uses that example. IDs and versions match case-insensitively; identical pins are fetched and returned once. Use NuGet normalized versions (`1.0.0`, not `1.0` or `1.0.0.0`); ranges/latest selectors, unknown keys and malformed inputs fail before requests. Public nuget.org only. Missing versions fail the complete batch visibly.

### Output

One complete row per unique package/version. `files` retains each source path, uncompressed length and compressed length; `fileCount` and totalUncompressedBytes summarize it. Archive size/hash/hash algorithm, listing/publication state, optional source licenseExpression, all target-framework direct dependency groups (including no-dependency groups), and observed `assetGroups` describe the inventory. Asset groups identify `lib`, `ref`, `runtimes`, `build`, `buildTransitive`, `analyzers`, `content`, `contentFiles` or other paths. Framework/RID labels are observed directory names, not a compatibility/build graph calculation. Source registration/catalogue/package-page URLs and timestamp retain provenance. SUMMARY supplies coverage, request count, transfer bytes and charge count.

### Limits

20 exact public package versions, 10,000 file entries per package, 41 requests including robots. Exact registration leaf then its linked catalogue item require no pagination; no archive is downloaded. 2MiB wire/4MiB decoded per response, 32MiB total wire, 64MiB decoded, 24MiB staged output. Acquisition deadline 180 seconds; delivery deadline 90 seconds; 30 seconds per request. No automatic retries. All selected pins are acquired and validated before delivery. Unexpected identity/host/path, duplicate file paths, malformed metadata, bounds, blocks, rate limits and timeout fail visibly; output is never silently truncated. Does not resolve transitive dependencies, prove framework compatibility, calculate per-file hashes or support private NuGet/GitHub/Azure feeds.

### Pricing

One `package-inventory` event at $0.002 per delivered complete package/version row. File entries and dependency groups are included. Duplicates, failed source requests and SUMMARY are not charged. No start fee or trial event. A PPE budget insufficient for all requested unique pins fails before acquisition. SDK delivery is not transactional; local accounting uses mocked storage/charges and is not real payment evidence.

### Privacy

Only public product metadata is returned. No package authors, owner profiles, contacts, package contents, authentication, cookies, browser, proxy or paid API. Links are source evidence and are not followed. Uses Microsoft's publicly supported NuGet API interfaces; no Microsoft endorsement is claimed.

# Actor input Schema

## `packages` (type: `array`):

1–20 public nuget.org packageId/version objects. Omitted input exports Newtonsoft.Json 13.0.3. Case-insensitive duplicate identities are returned once. Versions must use NuGet normalized spelling.

## Actor input object example

```json
{
  "packages": [
    {
      "id": "Newtonsoft.Json",
      "version": "13.0.3"
    }
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

Export exact NuGet versions into complete file paths and byte sizes, framework dependencies and runtime asset inventories without downloading package archives.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/nuget-package-file-dependency-export").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/nuget-package-file-dependency-export").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 '{}' |
apify call jpmarketdata/nuget-package-file-dependency-export --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/nuget-package-file-dependency-export"
        }
    }
}
```

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/Hi5s48MFrdsKsBw0f/builds/sQZpO9uPVbpS4Vdad/openapi.json