NuGet Packages Scraper

NuGet Packages Scraper

Scrape NuGet package metadata, version history, and download stats from any search query, owner, or author, up to a million packages per run. Every package comes with its full metadata, version list, and computed signals. No API key or registration required. Export to CSV, JSON, Excel, or XML.

The official NuGet API requires an API key for higher rate limits and returns paginated results you must stitch together yourself. This Actor reads the public NuGet catalog directly, filters by package type, prerelease status, owner, or author, and returns each matching package in one consistent flat schema.

Who uses it	What they scrape NuGet for
Developer tool vendors	Monitor competitor package releases and feature adoption.
Open-source maintainers	Track dependency chains and version usage across the .NET ecosystem.
Security researchers	Audit package metadata for deprecated or vulnerable dependencies.
Market analysts	Measure .NET library popularity and technology trends by package type.

What it does

This Actor collects NuGet packages by free-text search, owner, or author, and returns each one as a flat row with its metadata and version history.

• 🔍 Free-text search: Search across package IDs, titles, tags, authors, owners, and descriptions with a single query.
• 👤 Owner and author filters: Narrow results to packages owned or authored by a specific NuGet account, like 'microsoft' or 'aspnet'.
• 📦 Package type filter: Restrict results to a specific package type, such as .NET tool, template, or MSBuild SDK.
• 🔄 Version history: Collect up to 1000 versions per package, with prerelease inclusion controlled by a checkbox.
• 📊 Output limits: Cap the total packages collected per run, from a single test record up to one million.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with NuGet data

📈 Track .NET ecosystem trends.

A market analyst runs a weekly scrape for 'Dependency' type packages tagged 'machine learning' to identify which ML libraries are gaining traction in the .NET community.

🔒 Audit supply chain dependencies.

A security researcher scrapes all packages owned by a specific author to check for deprecated or unmaintained libraries before a compliance review.

🛠️ Monitor competitor tooling releases.

A developer tool vendor scrapes all 'DotnetTool' packages with a keyword query to track new competitor releases and feature updates.

📊 Build a NuGet intelligence dashboard.

A data engineer runs daily scrapes of the top 10,000 packages by relevance and feeds the metadata into an internal analytics dashboard for the development team.

Why choose this scraper

	What you get
Full metadata	Package ID, title, authors, owners, license, tags, and description.
Version history	Up to 1000 versions per package, with prerelease filtering.
Package type filtering	Target specific package types like .NET tools, templates, or MSBuild SDKs.
No API key	Reads the public NuGet catalog directly with no registration or rate-limit headaches.

How it compares

This Actor scrapes the public NuGet catalog directly with no API key, while the competitors below use the official NuGet API and focus on different subsets of metadata.

Feature	ParseForge	NuGet Package Stats	NuGet Package Intelligence API	NuGet Package Scraper
Free-text search across all package fields	Yes	Not listed	Not listed	Not listed
Filter by package type (tool, template, SDK, etc.)	Yes	Not listed	Not listed	Not listed
Filter by owner or author	Yes	Not listed	Not listed	Not listed
Version history with prerelease control	Yes	Yes	Yes	Not listed
No API key required	Yes	Not listed	Not listed	Not listed
Up to 1,000,000 packages per run	Yes	Not listed	Not listed	Not listed

Configure the run

Drive the Actor from a free-text search query, an owner, or an author, alone or together, and filters run as each package is read so only matches reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
  "semVerLevel": "2.0.0",
  "maxItems": 10
}

A larger pull:

{
  "semVerLevel": "2.0.0",
  "maxItems": 200
}

Pricing

Pay-per-result: $0.035 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$3.50
1,000 results	$35.00
10,000 results	$350.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the NuGet Packages Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to NuGet through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/nuget-packages-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check that your query, owner, or author filter is not too restrictive. Try broadening your search or setting the package type to 'Any' and enabling prerelease to see if results appear.

Why are some packages missing version history?

Ensure the 'Max versions per package' field is set high enough. If it is set to 0, all versions are kept. Also check that 'Include prerelease' is enabled if you expect preview versions.

The run stopped before collecting all packages I expected.

Check the 'Maximum packages' limit. The Actor stops once it reaches this number. Increase it up to 1,000,000 if you need more results.

Why do I see duplicate packages in my dataset?

The NuGet catalog may return the same package under different queries. Use the 'deduplicate' option in your dataset export or post-process the results to remove duplicates by package ID.

Can I filter by a specific SemVer version range?

The SemVer level setting controls which version format is honored, not a version range filter. To filter by version, scrape the full version history and filter the dataset after the run.

FAQ

Question	Answer
Do I need a NuGet API key to use this scraper?	No. This Actor reads the public NuGet catalog directly and does not require any API key, registration, or authentication.
Can I filter packages by a specific owner like Microsoft?	Yes. Use the Owner input field to restrict results to packages owned by a specific NuGet account, such as 'microsoft' or 'aspnet'.
Does it collect version history for each package?	Yes. You can set the maximum number of versions per package, up to 1000, and choose whether to include prerelease versions.
What package types can I filter by?	You can filter by Dependency (library), .NET tool, Template, MSBuild SDK, .NET client tool, .NET platform, Compatibility, and MSBuild task, or leave it on 'Any' to include all types.
How many packages can I scrape in one run?	You can set the maximum packages per run from 1 up to 1,000,000. The Actor will stop once it reaches that limit.
Can I search by keyword or package name?	Yes. The query field performs a free-text search across package IDs, titles, tags, authors, owners, and descriptions.
What output formats are supported?	You can export your dataset to CSV, JSON, Excel, or XML directly from the Apify platform.
Does it include download counts for each package?	The Actor returns the metadata and version history available in the public NuGet catalog. Download counts are included when present in the catalog data.
Can I combine multiple filters in one run?	Yes. You can combine a free-text query with an owner filter and a package type filter to narrow results precisely.
Is this scraper suitable for monitoring new package releases?	Yes. You can schedule regular runs with a query and the prerelease filter enabled to catch new and updated packages as they appear.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Microsoft Corporation. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.