npm Package Search Scraper is a BrowserAct Bot template for collecting structured package records from public npm search pages. Configure a keyword and result count, then run the Bot to return package metadata for developer tooling research, dependency discovery, market monitoring, or automation workflows.
What Does BrowserAct npm Package Search Scraper Do?
This template opens npm search results for your keyword, reads public package result data, follows pagination when needed, and returns one structured record per package.
Key Features
- Extract public npm package search results without requiring an npm login.
- Capture package name, URL, description, version, publisher, publish time, keywords, weekly downloads, license, and search keyword.
- Configure base URL, keyword, and count.
- Continue through paginated search results until the requested count is reached.
- Keep package records in search result rank order.
What Data Can I Extract from npm?
| Field | Description |
|---|---|
rank |
Package result position. |
package_name |
npm package name. |
package_url |
Public npm package URL. |
description |
Package description. |
version |
Visible package version. |
publisher |
Publisher or author name. |
published |
Relative publish or update time shown by npm. |
keywords |
Package keywords when available. |
weekly_downloads |
Weekly download count when available. |
license |
Package license when available. |
search_keyword |
Keyword used for the search run. |
How to Use npm Package Search Scraper
- Click Run task.
- Enter the search keyword.
- Set how many package records to collect.
- Run the Bot and review the structured 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.npmjs.com |
Base npm website URL without a trailing slash. |
keyword |
Yes | browser automation |
Search keyword or phrase. |
count |
Yes | 20 |
Maximum number of package records to return. |
Example Output
The table below uses records preserved from the validated Bot run. Up to the first 5 records are shown, and long values are shortened in this documentation preview.
| rank | package_name | package_url | description | version | publisher | published | keywords | weekly_downloads | license | search_keyword |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | agent-browser | https://www.npmjs.com/package/agent-browser | Browser automation CLI for AI agents | 0.34.0 | GitHub Actions | 9 days ago | browser, automation, headless, chrome, cdp, cli, agent | 1100281 | Apache-2.0 | browser automation |
How Does it Work?
BrowserAct constructs a public npm search URL from base_url and keyword, then opens the search results page in a live browser. The Bot reads package result data from the public page, maps metadata fields, and keeps records in rank order.
When count is higher than the first page of results, BrowserAct follows npm pagination and continues collecting records until the requested count is reached or no more public results are available. Fields that a package does not provide, such as license or keywords, are returned as empty values instead of blocking the run.
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 npm Package Search Results?
npm search data helps teams discover packages, compare developer tooling, monitor open-source ecosystems, research package adoption signals, and route dependency metadata into databases, dashboards, or agents.
Who Can Use This Template?
- Developer tool teams researching package ecosystems.
- Engineering teams comparing dependencies.
- Open-source analysts monitoring package visibility.
- Security or platform teams collecting package metadata.
- Automation builders routing package records into reports, alerts, databases, or agents.
How Many Results Can You Scrape?
Use count to control the number of package results returned. Higher counts may require pagination and can take longer than collecting only the first page.
Automation and Export
BrowserAct returns structured npm 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
