Libraries.io Package Scraper

Libraries.io Package Scraper

Scrape package metadata from Libraries.io across 19 package managers, up to a million projects per run. Every project comes with its stars, dependents, repository URL, latest release, and computed SourceRank. No login or API key required for specific packages. Export to CSV, JSON, Excel, or XML.

Libraries.io aggregates open source package data from npm, PyPI, Maven, Cargo, and 15 other registries, but its API needs a key and rate-limits you. This Actor reads the public API directly, filtered by platform, sort order, or exact package name, and returns each match in one fixed schema.

Who uses it	What they scrape Libraries.io for
Market researchers	Which libraries dominate a language ecosystem by stars and dependents
Developer tool vendors	Which packages to integrate with based on adoption and release cadence
Open source program offices	Which dependencies their teams use across package managers
Security analysts	Which packages need review based on latest release and repository activity
Data journalists	Which open source projects are trending in a given language

What it does

This Actor collects package metadata from Libraries.io by keyword search or exact package name, and returns each project as a flat row.

• 🔍 Keyword search: find packages by name, description, or keyword across all 19 supported package managers.
• 📦 Exact package lookup: pull metadata for specific packages like npm/react or pypi/django.
• 🏷️ Platform filter: restrict search to one registry, from npm to Julia.
• 📊 Sort options: order results by SourceRank, stars, dependents, dependent repos, latest release, or contributions.
• 🔑 API key support: use the shared key or bring your own free Libraries.io key for higher rate limits.

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

What you can do with Libraries.io data

📈 Track ecosystem trends.

A market researcher runs a keyword search for 'http client' across all platforms, sorts by stars, and sees which libraries lead each language.

🔍 Audit your dependencies.

An open source program office lists exact packages from their internal registry, pulls latest release dates, and flags anything stale.

🛡️ Prioritize security reviews.

A security analyst searches for packages with many dependents, then checks repository links to see which need deeper review.

📊 Compare package managers.

A developer tool vendor filters by platform, sorts by dependent repos, and decides which ecosystem to support next.

📰 Find stories in open source.

A data journalist searches for trending keywords, sorts by contributions, and identifies projects worth covering.

Why choose this scraper

	What you get
19 package managers	One schema for npm, PyPI, Maven, Cargo, and 15 more
Computed SourceRank	A single score that combines stars, dependents, and activity
Repository links	Direct URL to the source code for every package
Release data	Latest release date and version for each project
Flat output	One row per package, ready for CSV, JSON, Excel, or XML

How it compares

No other Store actor targets Libraries.io the same way, so the honest comparison is with the alternatives teams actually weigh.

	Libraries.io Package Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When Libraries.io changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Drive the Actor from search terms, exact package names, or both, and filters run as each project is read so only matches reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
  "searchTerms": [
    "http client"
  ],
  "maxItems": 10
}

A larger pull:

{
  "searchTerms": [
    "http client"
  ],
  "maxItems": 200
}

Pricing

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

Results collected	Approximate cost
100 results	$1.10
1,000 results	$11.00
10,000 results	$110.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 Libraries.io Package 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 Libraries.io 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/libraries-io-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 search terms are not too specific. Try a broader keyword, or remove the platform filter. Also verify that your API key is valid if you replaced the default.

Why is my run slow?

The Libraries.io API rate-limits requests. Use your own API key for higher limits, or reduce the 'Maximum projects' value.

Why do I get an authentication error?

The shared key may be rate-limited. Get a free key at libraries.io/account and enter it in the 'Libraries.io API key' field.

Why are some fields empty?

Not all packages have complete metadata on Libraries.io. Fields like repository URL or latest release may be missing for some projects.

Can I search for packages by description?

Yes. Keyword search matches package names, descriptions, and keywords. Use terms that appear in those fields.

FAQ

Question	Answer
Do I need a Libraries.io API key?	For keyword search, yes. The Actor includes a shared key by default, but you can get your own free key at libraries.io/account for higher rate limits. For exact package lookup, no key is required.
Which package managers are supported?	All 19 supported by Libraries.io: npm, PyPI, Maven, Go, NuGet, Packagist, Cargo, RubyGems, CocoaPods, Pub, Hex, Conda, CRAN, CPAN, Clojars, SwiftPM, Elm, and Julia.
Can I scrape a specific package?	Yes. List exact packages as 'platform/name', like npm/react or pypi/django. The Actor returns metadata for each one.
What is SourceRank?	SourceRank is Libraries.io's computed score that combines stars, dependents, dependent repos, and activity into a single number for comparing packages.
How many projects can I collect per run?	Up to 1,000,000. Set the 'Maximum projects' field to control the size of your dataset.
Can I filter search results by platform?	Yes. Use the 'Platform filter' to restrict keyword search to one package manager, or leave it as 'Any' to search all.
What sort orders are available?	SourceRank, stars, dependents, dependent repos, latest release, and contributions. Choose one in the 'Sort by' field.
What output formats are supported?	CSV, JSON, Excel, and XML. The Actor returns one flat row per package.
Does this Actor use the official Libraries.io API?	Yes. It reads the public API directly, so data is always current and matches what you see on libraries.io.
Can I run this on a schedule?	Yes. Use Apify's scheduler to run the Actor daily, weekly, or on any cron expression to keep your package data fresh.

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 Libraries.io. 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.