npm Package Scraper - Registry Search & Package Metadata
Pricing
from $2.00 / 1,000 results
npm Package Scraper - Registry Search & Package Metadata
Search the public npm registry or look up exact packages. Export versions, descriptions, maintainers, download counts, quality scores, links, licenses, and keywords. Built for research, benchmarking, and data pipelines. No login, cookies, or API keys — clean JSON output and pay-per-result pricing.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
Thirdwatch
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 hours ago
Last modified
Categories
Share
npm Package Scraper
Search npm packages and export versions, descriptions, maintainers, downloads, registry scores, repositories, licenses, and keywords.
What you get
Discover packages with registry search or resolve exact unscoped and scoped names. Search results include npm's download estimates and quality, popularity, and maintenance signals; exact lookups return the latest package metadata.
Output fields
| Field | Description |
|---|---|
name | npm package name |
version | Latest or returned version |
description | Package description |
keywords | Published keywords |
license | Published license for exact lookups |
date | Search index update date when available |
publisher | Publisher or author name |
maintainers | Maintainer names |
weekly_downloads | npm weekly download estimate |
monthly_downloads | npm monthly download estimate |
dependents | Reported dependent count |
score | Overall registry search score |
quality_score | Registry quality component |
popularity_score | Registry popularity component |
maintenance_score | Registry maintenance component |
npm_url | npm package page |
repository_url | Source repository when published |
homepage_url | Project homepage when published |
query | Search or exact package that produced the row |
source | Data-source name |
Example output
Input parameters
| Parameter | Required | Description |
|---|---|---|
queries | No | Registry searches such as web scraping or react table; web scraping is used only when both input modes are empty |
packageNames | No | Exact names such as react or @apify/actor |
maxResultsPerQuery | No | Results for each search, from 1 to 250; defaults to 20 |
Use cases
- Developers: compare packages before choosing a dependency.
- Engineering leaders: monitor important packages and versions.
- Researchers: measure ecosystem popularity and maintenance signals.
- Open-source teams: discover related projects and repositories.
Limitations
Search metrics are supplied by npm and can change independently. Exact lookups and discovery searches expose different upstream fields, so download and score fields can be empty on exact rows while license fields can be empty on search rows. Popularity is not evidence of security or suitability; inspect licenses, repositories, and advisories before adoption.
Compared to alternatives
Compared with benthepythondev/npm-package-scraper, this Actor supports exact scoped-package lookups as well as discovery search. Compared with seeb/npm-package-trend-monitor, it exports npm's search score components, maintainers, repository links, keywords, and download estimates for broader package research.
FAQ
Can I look up a scoped package?
Yes. Put the full name, such as @apify/actor, in packageNames.
Why is a license empty on a search result?
npm's discovery response does not always include it. Use an exact package lookup when license metadata is important.
Can I run multiple searches together?
Yes. Add several entries to queries; duplicate package names are removed.
Explore more at thirdwatch.dev. Related Actors: Google Search Scraper, Stack Exchange Questions Scraper, and Hacker News Scraper.
Last verified: 2026-07
