Packagist Packages Scraper

Export structured public Packagist Composer packages for discovery, comparison, monitoring, and governance.

What you get

Search the public Packagist catalog and save one deduplicated row per Composer package. Results include package name, description, type, downloads, favorites, current stable release, licenses, runtime requirements, maintainers, GitHub activity, support links, and dependency evidence. Use discovery inputs for market maps and exact-name inputs, when available, for stable monitoring cohorts.

Output fields

Field group	Description
Identity	Canonical name, display name, and source URL.
Release evidence	Current version or tag data and source timestamps when published.
Adoption signals	Public download, install, pull, star, or rating metrics available from the source.
Ownership and links	Public author, owner, project, repository, documentation, or homepage references.
Classification	Public tags, categories, keywords, packaging, or status values.
Provenance	Search query and named upstream source for traceable analysis.

Example output

{"name":"laravel/framework","latestVersion":"v12.0.0","licenses":["MIT"],"downloadsTotal":500000000,"downloadsMonthly":20000000,"githubStars":34000,"requirements":{"php":"^8.2"},"repository":"https://github.com/laravel/framework","url":"https://packagist.org/packages/laravel/framework"}

Input parameters

Parameter	Required	Description
queries	No	Up to five Composer package search phrases.
packageNames	No	Up to 25 exact vendor/package names or URLs.
includeDetails	No	Enrich discovery rows with releases, licenses, and requirements; defaults to true.
maxResultsPerQuery	Yes	Maximum packages per query; defaults to 25.
maxResults	Yes	Maximum unique packages across all modes; defaults to 100.

At least one discovery or exact-name input is required. Result limits apply after cross-input deduplication, and only saved unique rows are charged.

Use cases

• Developers: discover alternatives and compare public release evidence.
• Platform teams: monitor versions, tags, compatibility, and activity for a fixed portfolio.
• Security teams: build an evidence inventory before joining vulnerability and deployment data.
• Product researchers: map a developer ecosystem with repeatable queries and dated snapshots.

Limitations

Only public Packagist metadata is covered. Composer author email fields are discarded, package requirements are evidence rather than a resolved lockfile, and license strings still require policy interpretation.

Compared to alternatives

Current Apify Store alternatives include benthepythondev/packagist-packages-scraper and outstanding_vegetable/packagist-scraper. Thirdwatch combines discovery and bounded monitoring inputs where the source permits them, saves canonical evidence URLs, deduplicates before charging, provides exactly four PPE tiers, and ships ten ready-to-save Task recipes plus a five-article workflow library. Compare current Store listings directly because competitor features and pricing can change.

FAQ

Does this Actor access private packages or accounts?

No. It collects only metadata available from the public source and does not sign in, bypass access controls, or request private registry credentials.

How should I monitor a fixed portfolio?

Use exact names where supported, keep result limits explicit, save the input as an Apify Task, and retain dated datasets. Do not let an empty or failed run overwrite the previous successful snapshot.

Are popularity metrics quality or security scores?

No. Downloads, installs, pulls, stars, and ratings help prioritize review, but they do not replace vulnerability, provenance, license, maintainership, or internal deployment evidence.

Where can I find more workflows?

Visit Thirdwatch developer-data scrapers and the related GitHub, npm, and OSV Actors.

Last verified: 2026-07