Pub.dev Package Scraper — Dart & Flutter Package Metadata, Scores & Dependencies

The Pub.dev Package Scraper extracts structured metadata for Dart and Flutter packages from the public Pub.dev API. It is built for mobile developers, DevOps teams, security researchers, and data analysts who need to inventory Flutter dependencies, track package popularity, compare SDK constraints, or monitor the Dart ecosystem.

This Actor accepts a list of Pub.dev package names (for example, bloc, http, provider, shared_preferences) and returns a clean dataset with the latest version, description, publisher, license, SDK constraints, dependency counts, topic tags, source links, and Pub.dev score data including likes and 30-day downloads. You can also supply a search query to discover packages through Pub.dev search before extraction.

Use Cases

• Dependency inventory — Audit every Dart and Flutter package used across your organization and export the results to a spreadsheet, SIEM, or data warehouse.
• Supply-chain monitoring — Track new releases, deprecated packages, license changes, and SDK compatibility for critical dependencies.
• Competitive research — Compare Pub.dev scores, likes, and download counts to identify the most trusted and widely adopted libraries in the Flutter ecosystem.
• Security triage — Flag discontinued packages and outdated SDK constraints that may need upgrading or replacement.
• Dataset creation — Build a structured corpus of Flutter package metadata for research, search, or internal tooling.
• Migration planning — Collect SDK constraints (Dart and Flutter) across a package list to plan version upgrades.

Input

Field	Type	Required	Description
packageNames	Array	Yes	Pub.dev package names to scrape, e.g., ["bloc", "http", "provider"]
searchQuery	String	No	Pub.dev search query used to discover additional packages
maxItems	Number	No	Maximum results to output (default: 100)
includeScore	Boolean	No	Fetch Pub.dev score, likes, and 30-day downloads (default: true)
includePublisher	Boolean	No	Fetch the verified publisher ID for each package (default: true)
proxyConfiguration	Object	No	Apify proxy configuration (recommended for production runs)

Output

The Actor outputs a dataset with one row per Pub.dev package:

{
  "packageName": "bloc",
  "latestVersion": "9.2.1",
  "description": "A predictable state management library that helps implement the BLoC design pattern.",
  "publisherId": "bloclibrary.dev",
  "license": "mit",
  "publishedAt": "2025-10-15T00:00:00.000Z",
  "sdkConstraint": ">=2.14.0 <4.0.0",
  "dartConstraint": ">=2.14.0 <4.0.0",
  "flutterConstraint": "",
  "homepageUrl": "https://github.com/felangel/bloc",
  "repositoryUrl": "https://github.com/felangel/bloc/tree/master/packages/bloc",
  "issueTrackerUrl": "https://github.com/felangel/bloc/issues",
  "documentationUrl": "https://bloclibrary.dev",
  "dependencyCount": 1,
  "devDependencyCount": 3,
  "dependencyNames": "meta",
  "devDependencyNames": "bloc_lint, mocktail, test",
  "topicCount": 2,
  "topics": "bloc, state-management",
  "grantedPoints": 160,
  "maxPoints": 160,
  "likeCount": 3201,
  "downloadCount30Days": 1881848,
  "tags": "is:flutter-favorite, publisher:bloclibrary.dev, sdk:dart, sdk:flutter, platform:android, platform:ios, platform:web, license:mit",
  "deprecated": false,
  "url": "https://pub.dev/packages/bloc"
}

Pricing

Pay per event: $0.001 per package extracted. The Actor charges only after successfully extracting metadata, so you never pay for failed or empty requests.

Limitations

• The Actor relies on the public Pub.dev API. Availability and rate limits are governed by Google.
• Package names must match the canonical Pub.dev slug exactly (e.g., shared_preferences, not Shared Preferences).
• Score, publisher, and version detail endpoints add one extra API call each per package.
• The license field is extracted from the pubspec or Pub.dev score tags when available.

FAQ

Q: Do I need a Pub.dev account? A: No. The public Pub.dev API does not require authentication.

Q: Can I scrape all Pub.dev packages at once? A: The Actor is designed for targeted lists or search queries. Use maxItems to cap output and respect API limits.

Q: Why are some fields empty? A: Pub.dev maintainers provide metadata voluntarily. If a field such as homepageUrl or repositoryUrl is missing from the upstream package, the output will be blank.

Changelog

• v1.0.0 — Initial release: package metadata, version details, Pub.dev scores, publisher IDs, dependencies, and source links.