NuGet Package Search Scraper is a BrowserAct Bot template for collecting structured .NET package records from public NuGet search results. Configure a keyword and result count, then run the Bot to return ranked package metadata for dependency research, ecosystem monitoring, package discovery, developer tooling, or automation workflows.
What Does BrowserAct NuGet Package Search Scraper Do?
This template opens NuGet search for your keyword, extracts public package result cards, follows pagination when needed, and returns one structured record per package.
Key Features
- Extract public NuGet search results without requiring a login.
- Capture rank, package ID, package URL, description, owners, downloads, latest version, verified status, tags, last updated time, and search keyword.
- Configure base URL, keyword, and count.
- Continue through NuGet result pages until the requested count is reached.
- Keep package metadata ready for .NET dependency review, dashboards, and agent workflows.
What Data Can I Extract from NuGet?
| Field | Description |
|---|---|
rank |
Search result position. |
package_id |
NuGet package ID. |
package_url |
Public NuGet package URL. |
description |
Package description shown on the search card. |
owners |
Owners or authors shown by NuGet. |
total_downloads |
Total download count shown by NuGet. |
latest_version |
Latest version shown on the result card. |
verified |
Whether the package is shown as verified. |
tags |
Tags visible on the result card. |
last_updated |
Last updated time shown by NuGet. |
search_keyword |
Keyword used for the run. |
How to Use NuGet Package Search Scraper
- Click Run task.
- Enter the NuGet base URL.
- Enter a package, framework, library, or .NET ecosystem keyword.
- Set how many package records to collect.
- Run the Bot and review the structured NuGet package results.
- Reuse the Bot with another keyword or connect the output to your workflow.
Input Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
base_url |
Yes | https://www.nuget.org |
NuGet base URL without a trailing slash. |
keyword |
Yes | json |
Search keyword sent as the q parameter. |
count |
Yes | 20 |
Maximum number of package records to return. |
Example Output
{
"results": [
{
"rank": 1,
"package_id": "Newtonsoft.Json",
"package_url": "https://www.nuget.org/packages/Newtonsoft.Json/13.0.5-beta1",
"description": "Json.NET is a popular high-performance JSON framework for .NET",
"owners": "dotnetfoundation, jamesnk, newtonsoft",
"total_downloads": "8969352212",
"latest_version": "13.0.5-beta1",
"verified": true,
"tags": "json",
"last_updated": "8 months ago",
"search_keyword": "json"
}
]
}
How Does it Work?
BrowserAct constructs a public NuGet search URL from base_url and keyword, opens the search results page, and reads each visible package result card. The Bot maps each card into a ranked record with package ID, URL, description, owners, downloads, latest version, verified status, tags, last updated time, and keyword.
When count is higher than the first result page, BrowserAct follows NuGet pagination using the public page parameter. The Bot stops when it reaches the requested count or when a page has no more public package result cards.
How to Build a New Scraper Bot with Agent Built
Step 1: Describe the Data You Need
Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Paste a clear request that includes the website, the records to collect, the filters or search conditions, the fields to return, the result limit, and the inputs you want to reuse later.
Step 2: Let BrowserAct Build and Test the Bot
BrowserAct explores the live website, works out the navigation and extraction path, and validates the result. If BrowserAct asks for clarification, reply in the same build conversation with the missing URL, condition, field, example, or expected output.
Step 3: Run the Bot and Review the Result
When the build is complete, run the Bot with the default inputs first. Review the structured records, source URLs, missing fields, and row count before reusing the Bot with new inputs or connecting it to another workflow.
Why Scrape NuGet Package Search Results?
NuGet search data helps teams discover .NET packages, compare package popularity, monitor ecosystem activity, review dependency candidates, and route package metadata into developer reports, dependency dashboards, or agent workflows.
Who Can Use This Template?
- .NET developers researching libraries and alternatives.
- Platform teams building internal package catalogs.
- Security and dependency teams reviewing public package metadata.
- Developer tooling teams monitoring ecosystem trends.
- Automation builders routing package data into spreadsheets, databases, alerts, or agents.
How Many Results Can You Scrape?
Use count to control the number of NuGet package records returned. NuGet typically shows 20 results per page, and BrowserAct follows pagination until the requested count is reached or no more public results are available.
Automation and Export
BrowserAct returns structured NuGet package records first. You can then use the output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual CSV review.
Need Help?
Contact us at
Discord: Discord Community
E-mail: service@browseract.com
