crates.io Scraper - Rust Package Metadata

Scrape crates.io Rust package metadata with crate name, description, downloads, version, license, repository and documentation URL. Export the data to JSON, CSV, Excel, webhooks, Make, Zapier, n8n, Google Sheets or your own API.

Package registries are useful demand signals. Developers use them to choose libraries, security teams use them to watch dependency ecosystems, investors and analysts use them to track technology adoption, and developer-tool companies use them to find projects that match their integration or migration targets. This actor turns crates.io search results into a clean Apify dataset that is easy to schedule, enrich and join with other sources.

What does this actor do?

The actor queries crates.io's public search endpoint and normalizes package metadata into flat rows. You provide a query such as tokio, set the maximum number of results, and the actor returns package names, descriptions and source-specific popularity or version fields. The implementation is intentionally lightweight: direct HTTP requests, no browser, no proxy, no account and no API key.

Input

{
  "query": "tokio",
  "maxResults": 25
}

Use specific framework, language, company, tool or technology names for targeted research. Broad terms return popular ecosystem packages; narrow terms are better for lead generation and competitor tracking.

Output

Each item includes a stable package identifier, package name, description, source name, the original query and source-specific fields such as downloads, versions, repository URL, homepage URL, license, documentation URL or tags when the registry provides them.

{
  "package_id": "example/package",
  "name": "example/package",
  "description": "Example package description",
  "source": "crates.io",
  "search": "tokio"
}

Use cases

Developer-relations teams can identify packages in an ecosystem and build outreach lists. Security teams can monitor packages by keyword and spot high-download dependencies. SaaS companies can find open-source projects that might need an integration, migration tool, hosting service or support product. Market researchers can track which frameworks, libraries and tool categories are growing across public package registries.

Scheduling

Run the actor weekly for the same query and append results to a dataset. Over time, downloads, versions and repository metadata create a useful time series for ecosystem research. You can also trigger webhooks when a search returns a new package matching your target keyword.

Reliability

This actor uses public registry endpoints and small default inputs so daily auto-tests remain fast. It retries transient request errors and pushes one dataset item per package result. Because it does not use browser automation or residential proxies, it is inexpensive to run and suitable for scheduled tasks.

Pricing

This actor uses pay-per-result pricing. You pay for each package row written to the dataset, plus a small actor start event.

FAQ

Does it need an API key?

No. It uses public package registry endpoints.

Can I search any keyword?

Yes. Use package names, framework names, vendors, technologies or broad category terms.

Can this monitor new packages?

Yes. Schedule the same query and compare outputs over time.

Is it useful for lead generation?

Yes. Package metadata can identify projects, maintainers, repositories and ecosystems relevant to developer-tool sales and partnerships.

You might also like

• PyPI Scraper
• Docker Hub Scraper
• GitHub Repository Intelligence

Keywords

crates.io scraper, package metadata API, open source intelligence, developer tools data, package registry scraper, dependency research, software ecosystem data, Apify package scraper.

Data quality notes

The actor keeps the output intentionally flat so it can be joined with CRM records, enrichment tools, spreadsheets and BI systems without additional parsing. Identifiers are stable where the source registry provides them, and source-specific fields are preserved instead of being hidden behind a generic schema. This makes the dataset useful for both quick exports and repeatable monitoring workflows.

For lead-generation use, combine the package name and repository/homepage fields with a contact enrichment actor such as Website Contact Extractor. For market research, schedule the same query over time and compare downloads, version counts, favorites or timestamps. For developer-relations work, use keyword searches around frameworks, cloud providers, databases, AI tooling, testing libraries or migration targets to find projects that match your product category.

Tips for better searches

Use broad ecosystem terms when you want market maps, for example api, database, testing, ai, payments, kubernetes or analytics. Use exact package or framework terms when you want competitor monitoring. Run several narrow queries instead of one huge query when you need better coverage across a category.

Automation ideas

You can run this actor from Apify schedules, the API, a saved task, or an integration. Common workflows include weekly package tracking, dependency research, open-source lead discovery, security watchlists, trend dashboards and technology adoption reports. The actor is small enough to run frequently and cheap enough to include in larger enrichment pipelines.

Why this dataset has commercial value

Package metadata is a buying-intent signal for developer products. A project that depends on a framework, database, cloud service, testing tool or API category often has an active engineering team and an immediate technical context. That makes registry data useful beyond simple package lookup: it can feed sales research, partner discovery, ecosystem mapping, migration planning, content targeting and competitive analysis.

For best results, combine registry rows with repository metadata, website contact extraction and company enrichment. The package registry tells you what technology is being used; enrichment tells you who owns the project and how to reach them. That combined workflow is where these lightweight package actors become useful business tools instead of one-off lookup scripts.