NuGet Scraper - .NET Packages, Downloads & Authors

Scrape the NuGet .NET package registry in bulk. Extract package ID, title, version, description, authors, owners, total downloads, tags, licence and project links, verification status and known vulnerabilities to CSV/JSON. No API key.

---

What does the NuGet Scraper do?

This Actor turns NuGet data into a structured dataset. You point it at the whole registry or by keyword, it walks the result pages one after another, and it writes one clean row per package into your dataset — ready to export as JSON, CSV or Excel, or to pull straight from the Apify API.

NuGet is the package registry behind .NET, and its search service answers without a key over roughly 488,000 packages. The response carries the full version history for every package, which is what makes a hundred-result page weigh more than a megabyte — the Actor keeps the version count and the latest version and drops the rest, so exports stay small without losing the numbers that matter. Pagination is followed automatically until it runs out of results, hits your page limit or hits your Max items cap, whichever comes first. Every row is de-duplicated across the whole run, so you are never billed twice for the same package.

There is no API key, no login and no browser involved. That keeps runs fast and cheap, and it means you can schedule the Actor without worrying about credentials expiring.

Who is it for?

• .NET architects vetting packages before taking a dependency.
• Security teams flagging packages that ship known vulnerabilities.
• Developer-relations teams tracking adoption of competing libraries.
• Market researchers measuring the .NET ecosystem.
• Developers building package-intelligence tooling.

Use cases

• Export every package for a keyword and rank by total downloads.
• Find packages that carry known vulnerabilities.
• Compare download counts across competing libraries.
• Measure how crowded a package category already is.
• Build a shortlist with licence and author context attached.

Why use this NuGet Scraper?

• 🔑 Keyless — no account, no API token, no cookies to paste.
• 📦 20 fields per package — everything the source exposes, already typed.
• 📄 Real pagination — it walks page after page instead of returning the first screen.
• 🎯 Precise caps — Max items stops the run exactly where you want it, so the bill is predictable.
• 📊 Export anywhere — JSON, CSV, Excel or HTML, plus the Apify API and integrations.
• 💸 Pay per result — you pay for rows you actually receive, with no platform fees to calculate.

What data can you extract?

Every run produces one row per package, with these fields:

Field	Type	Description
packageId	string	NuGet package identifier
title	string	Display title when the author set one
version	string	Latest published version
description	string	Package description
summary	string	Short summary when published
authors	string	Authors, separated by a pipe
owners	string	Registry owners, separated by a pipe
totalDownloads	number	Lifetime downloads across all versions
versionCount	number	Number of published versions
isVerified	boolean	Whether the package prefix is reserved and verified
vulnerabilityCount	number	Known vulnerabilities reported by NuGet
packageTypes	string	Package types, e.g. Dependency or Template
tags	string	Author tags, separated by a pipe
projectUrl	string	Project homepage
licenseUrl	string	Licence link when published
iconUrl	string	Package icon URL
packageUrl	string	nuget.org page for the package
query	string	Search term this row came from
page	number	Result page the package appeared on
scrapedAt	string	ISO timestamp of extraction

Output example

{
  "packageId": "Newtonsoft.Json",
  "title": "Json.NET",
  "version": "13.0.4",
  "description": "Json.NET is a popular high-performance JSON framework for .NET",
  "summary": null,
  "authors": "James Newton-King",
  "owners": "dotnetfoundation | jamesnk | newtonsoft",
  "totalDownloads": 9246414287,
  "versionCount": 53,
  "isVerified": true,
  "vulnerabilityCount": 0,
  "packageTypes": "Dependency",
  "tags": "json",
  "projectUrl": "https://www.newtonsoft.com/json",
  "licenseUrl": "https://www.nuget.org/packages/Newtonsoft.Json/13.0.4/license",
  "iconUrl": "https://api.nuget.org/v3-flatcontainer/newtonsoft.json/13.0.4/icon",
  "packageUrl": "https://www.nuget.org/packages/Newtonsoft.Json",
  "query": "whole registry",
  "page": 1,
  "scrapedAt": "2026-09-21T10:18:44.902Z"
}

How to use

Option A — the whole registry

{
  "includePrerelease": false,
  "maxItems": 2000,
  "maxPagesPerSearch": 20,
  "searchTerms": []
}

1. Open the Actor and fill in the first field.
2. Set the page limit and Max items to bound the run.
3. Click Start, then export from the Output tab.

Option B — by keyword

{
  "includePrerelease": false,
  "maxItems": 1000,
  "maxPagesPerSearch": 10,
  "searchTerms": [
    "logging",
    "json",
    "orm"
  ]
}

Everything in the first field is processed independently, so you can batch several targets into one run and split them apart afterwards.

Input parameters

Parameter	Type	Default	Description
searchTerms	array	[]	Terms to search NuGet for, e.
includePrerelease	boolean	false	Include beta and preview packages.
maxPagesPerSearch	integer	4	How many result pages to walk for each search.
maxItems	integer	500	Stop after this many packages.
maxConcurrency	integer	2	Parallel requests.
proxyConfiguration	object	{"useApifyProxy": true}	Proxy used to fetch pages.

Tips for best results

• Leave the search term empty to walk the whole registry — roughly 488,000 packages.
• The API returns up to 100 packages per page; larger pages exceed a megabyte and start timing out.
• Include prerelease adds beta and preview packages, which are excluded by default.
• totalDownloads is lifetime across every version, so it favours older packages.
• vulnerabilityCount above zero is the fastest way to build a review list.
• isVerified means the package prefix is reserved by its owner — a useful trust signal.
• The full version history is deliberately not exported; versionCount and version carry the same signal at a fraction of the size.
• tags are author-supplied and inconsistent, so treat them as hints rather than a taxonomy.
• Schedule a weekly run and append to one dataset to build a download-history series.
• Pair with the npm and Maven Central scrapers to compare ecosystems.

Run outcomes: an empty result is not the same as a blocked run

A crawl that was refused and a query that genuinely has no matches both produce an empty dataset. Treating them as the same thing makes the output unusable for monitoring, so every run is classified and an unverified emptiness is never reported as success.

Outcome	Run status	Meaning
COMPLETED	Succeeded	Everything requested was fetched and rows were saved.
PARTIAL	Succeeded	Rows were saved, but some pages were unreachable.
EMPTY_RESULT	Succeeded	Pages were fetched and parsed and this query really has no packages.
BLOCKED	Failed	Every request was refused with HTTP 403/429/503.
NOT_FOUND	Failed	The source answered 404; check the address or filters.
FETCH_FAILED	Failed	Nothing could be fetched for transport reasons.
INCOMPLETE_NO_ROWS	Failed	Pages were skipped and nothing was saved, so an empty result cannot be trusted.

The rule behind the table: a run that fetched nothing can never finish as Succeeded. Each run also writes a SUMMARY record to the key-value store with pages requested, pages fetched, pages skipped, HTTP request and retry counts, a per-status breakdown, transport errors and the termination reason — so the row count is always reconcilable with what the run actually did.

Integrations

Send results straight into the tools you already use: Google Sheets, Slack, Zapier, Make, Airtable or any Webhook. You can also schedule the Actor to run hourly, daily or weekly and have each run append to the same dataset, which is how you build a price or availability history rather than a one-off snapshot.

API usage

Run the Actor and collect results from any language. Replace <YOUR_TOKEN> with your Apify API token.

cURL

curl -X POST "https://api.apify.com/v2/acts/logiover~nuget-package-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"includePrerelease": false, "maxItems": 2000, "maxPagesPerSearch": 20, "searchTerms": []}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_TOKEN>' });
const run = await client.actor('logiover/nuget-package-scraper').call({"includePrerelease": false, "maxItems": 2000, "maxPagesPerSearch": 20, "searchTerms": []});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('<YOUR_TOKEN>')
run = client.actor('logiover/nuget-package-scraper').call(run_input={"includePrerelease": false, "maxItems": 2000, "maxPagesPerSearch": 20, "searchTerms": []})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Use with AI agents (MCP)

This Actor is available through the Apify MCP server, so an AI agent can call it as a tool. Point your agent at https://mcp.apify.com and it can run the NuGet Scraper on demand — for example: "Pull the first 500 packages from NuGet and summarise what you find." The agent receives the same structured rows you would get from the UI.

FAQ

Do I need a NuGet account or API key?

No. The Actor reads publicly available data only. There is nothing to authenticate and no credentials to rotate.

How many packages can I get in one run?

As many as the source exposes. Raise the page limit and Max items together; the run stops at whichever limit it reaches first.

Why did I get fewer rows than I asked for?

The source ran out of packages. That is normal for narrow searches — broaden the query or add more targets to one run.

Are results de-duplicated?

Yes. Each package is emitted once per run, even when it appears on several pages, so you are never billed twice for the same record.

Why are some fields empty?

NuGet does not publish every attribute for every package. Empty means the source did not supply it, not that extraction failed.

What export formats are supported?

JSON, CSV, Excel, HTML and RSS from the Output tab, plus the Apify API and any integration you connect.

How fast is it?

It is pure HTTP with no browser, so a page of results typically takes a second or two. Raise Max concurrency carefully — the source rate-limits aggressive crawling.

Can I schedule it?

Yes. Use the Apify scheduler to run it on any interval and append each run to the same dataset for time-series analysis.

Does it work behind a proxy?

It uses Apify Proxy automatically. You can switch groups or supply your own proxies in Proxy configuration.

How often does the data change?

NuGet updates continuously. Re-run whenever you need current data; the Actor always reads the live source, never a cache.

Is the output schema stable?

Yes. Field names and types are fixed, so downstream pipelines will not break between runs.

What if the source changes its format?

Open an issue on the Issues tab and it gets fixed. The Actor is actively maintained.

Is it legal?

This Actor reads only publicly available data from NuGet — the same content any visitor or client sees without logging in. It does not bypass authentication, does not collect private data and does not attempt to defeat access controls. You are responsible for how you use the output: respect the source's terms of service, applicable copyright, and data-protection law such as GDPR where personal data is involved. Scraping public data is generally lawful in the EU and the US, but the responsibility for the downstream use of that data sits with you.

Related scrapers

• Maven Central Scraper — JVM registry
• npm Package Intelligence — JavaScript registry
• PyPI Package Scraper — Python registry
• crates.io Scraper — Rust registry