# Packagist Scraper - PHP Packages, Downloads & Stars (`logiover/packagist-php-package-scraper`) Actor

Scrape the Packagist PHP package registry in bulk. Extract package name, vendor, description, repository, total downloads, favers, GitHub stars and forks, language, maintainers and release history to CSV/JSON. No API key.

- **URL**: https://apify.com/logiover/packagist-php-package-scraper.md
- **Developed by:** [Logiover](https://apify.com/logiover) (community)
- **Categories:** Developer tools, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Packagist Scraper - PHP Packages, Downloads & Stars

![Apify Actor](https://img.shields.io/badge/Apify-Actor-00A67E?logo=apify\&logoColor=white) ![No API key](https://img.shields.io/badge/No%20API%20key-required-2ea44f) ![Pay per result](https://img.shields.io/badge/Pricing-Pay%20per%20result-1C7ED6) ![Export](https://img.shields.io/badge/Export-JSON%20%7C%20CSV%20%7C%20Excel-F59E0B)

**Scrape the Packagist PHP package registry in bulk. Extract package name, vendor, description, repository, total downloads, favers, GitHub stars and forks, language, maintainers and release history to CSV/JSON. No API key.**

***

### What does the Packagist Scraper do?

This Actor turns Packagist data into a structured dataset. You point it at the registry with full details or several topics, names only, it walks the result pages one after another, and it writes one clean row per package into your dataset — ready to export as JSON, CSV or Excel, or to pull straight from the Apify API.

Packagist is the registry behind Composer and every PHP project that uses it, and it answers a keyless search API covering more than 368,000 packages. The search response carries only six fields, so the Actor optionally enriches each row from the package's own endpoint — GitHub stars, language, maintainers and release history — which is what turns a name list into usable ecosystem data. Pagination is followed automatically until it runs out of results, hits your page limit or hits your **Max items** cap, whichever comes first. Every row is de-duplicated across the whole run, so you are never billed twice for the same package.

There is **no API key, no login and no browser** involved. That keeps runs fast and cheap, and it means you can schedule the Actor without worrying about credentials expiring.

### Who is it for?

- **PHP library authors** sizing a niche before building.
- **Agencies and CTOs** vetting dependencies before adopting them.
- **Market researchers** measuring the PHP ecosystem.
- **Security teams** finding widely used but unmaintained packages.
- **Developer-relations teams** tracking competing libraries.

### Use cases

- Export every package for a tag and rank by download count.
- Find high-download packages with no release in years.
- Compare stars against downloads to spot hype versus real use.
- Measure how crowded a package category already is.
- Build a dependency shortlist with maintainer and licence context.

### Why use this Packagist Scraper?

- 🔑 **Keyless** — no account, no API token, no cookies to paste.
- 📦 **23 fields per package** — everything the source exposes, already typed.
- 📄 **Real pagination** — it walks page after page instead of returning the first screen.
- 🎯 **Precise caps** — **Max items** stops the run exactly where you want it, so the bill is predictable.
- 📊 **Export anywhere** — JSON, CSV, Excel or HTML, plus the Apify API and integrations.
- 💸 **Pay per result** — you pay for rows you actually receive, with no platform fees to calculate.

### What data can you extract?

Every run produces one row per package, with these fields:

| Field | Type | Description |
|-------|------|-------------|
| `name` | string | Full package name, vendor and package |
| `vendor` | string | Vendor part of the package name |
| `packageName` | string | Package part of the name |
| `description` | string | Package description |
| `packageUrl` | string | Packagist page for the package |
| `repository` | string | Source repository URL |
| `downloads` | number | Total downloads reported by Packagist |
| `favers` | number | Number of users who favourited the package |
| `packageType` | string | Composer package type, e.g. library or symfony-bundle |
| `language` | string | Primary language reported by the repository host |
| `githubStars` | number | Stars on the source repository |
| `githubForks` | number | Forks on the source repository |
| `githubOpenIssues` | number | Open issues on the source repository |
| `maintainers` | string | Maintainer usernames, separated by a pipe |
| `latestVersion` | string | Most recent published version |
| `versionCount` | number | Number of published versions |
| `lastReleaseAt` | string | Timestamp of the most recent release |
| `dependentCount` | number | Packages that depend on this one |
| `suggesterCount` | number | Packages that suggest this one |
| `isAbandoned` | boolean | Whether the package is marked abandoned |
| `query` | string | Search term or filter this row came from |
| `page` | number | Result page the package appeared on |
| `scrapedAt` | string | ISO timestamp of extraction |

#### Output example

```json
{
  "name": "symfony/polyfill-mbstring",
  "vendor": "symfony",
  "packageName": "polyfill-mbstring",
  "description": "Symfony polyfill for the Mbstring extension",
  "packageUrl": "https://packagist.org/packages/symfony/polyfill-mbstring",
  "repository": "https://github.com/symfony/polyfill-mbstring",
  "downloads": 1285711537,
  "favers": 7832,
  "packageType": "library",
  "language": "PHP",
  "githubStars": 7817,
  "githubForks": 39,
  "githubOpenIssues": 1,
  "maintainers": "fabpot",
  "latestVersion": "v1.38.2",
  "versionCount": 50,
  "lastReleaseAt": "2026-05-27T06:59:30+00:00",
  "dependentCount": 548,
  "suggesterCount": 33,
  "isAbandoned": false,
  "query": "type: library",
  "page": 1,
  "scrapedAt": "2026-09-20T12:41:55.203Z"
}
```

### How to use

#### Option A — the registry with full details

```json
{
  "includeDetails": true,
  "maxItems": 300,
  "maxPagesPerSearch": 3,
  "packageType": "library",
  "searchTerms": []
}
```

1. Open the Actor and fill in the first field.
2. Set the page limit and **Max items** to bound the run.
3. Click **Start**, then export from the **Output** tab.

#### Option B — several topics, names only

```json
{
  "includeDetails": false,
  "maxItems": 2000,
  "maxPagesPerSearch": 20,
  "searchTerms": [
    "logging",
    "orm",
    "http"
  ]
}
```

Everything in the first field is processed independently, so you can batch several targets into one run and split them apart afterwards.

### Input parameters

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `searchTerms` | array | `[]` | Terms to search Packagist for, e. |
| `packageType` | string | `library` | Composer type used when no search term is given. |
| `tag` | string | `–` | Narrow to a Packagist tag such as logging, testing or http. |
| `includeDetails` | boolean | `true` | Fetch stars, language, maintainers and release history for each package. |
| `maxPagesPerSearch` | integer | `3` | How many result pages to walk for each search. |
| `maxItems` | integer | `300` | Stop after this many packages. |
| `maxConcurrency` | integer | `2` | Parallel requests. |
| `proxyConfiguration` | object | `{"useApifyProxy": true}` | Proxy used to fetch pages. |

### Tips for best results

- Leave the search term empty to walk the whole registry by package type.
- **Package type** `library` covers the bulk of Packagist — over 368,000 entries.
- **Tag** narrows to a topic such as logging, orm or testing.
- The search API returns 100 packages per page but only six fields per package.
- **Include package details** adds stars, language, maintainers and versions at roughly a third of a second per package, so it is the setting that decides run length.
- Turn details off for a fast name-and-downloads sweep of a large category.
- High `downloads` with an old `lastReleaseAt` is the classic abandoned-but-depended-on signal.
- `isAbandoned` is set explicitly by maintainers and is worth filtering on.
- `githubStars` is empty for packages hosted outside GitHub — that is the source, not extraction.
- Pair with the npm and PyPI scrapers to compare ecosystems side by side.

### Integrations

Send results straight into the tools you already use: **Google Sheets**, **Slack**, **Zapier**, **Make**, **Airtable** or any **Webhook**. You can also **schedule** the Actor to run hourly, daily or weekly and have each run append to the same dataset, which is how you build a price or availability history rather than a one-off snapshot.

### API usage

Run the Actor and collect results from any language. Replace `<YOUR_TOKEN>` with your Apify API token.

**cURL**

```bash
curl -X POST "https://api.apify.com/v2/acts/logiover~packagist-php-package-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"includeDetails": true, "maxItems": 300, "maxPagesPerSearch": 3, "packageType": "library", "searchTerms": []}'
```

**Node.js**

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_TOKEN>' });
const run = await client.actor('logiover/packagist-php-package-scraper').call({"includeDetails": true, "maxItems": 300, "maxPagesPerSearch": 3, "packageType": "library", "searchTerms": []});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

**Python**

```python
from apify_client import ApifyClient

client = ApifyClient('<YOUR_TOKEN>')
run = client.actor('logiover/packagist-php-package-scraper').call(run_input={"includeDetails": true, "maxItems": 300, "maxPagesPerSearch": 3, "packageType": "library", "searchTerms": []})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)
```

### Use with AI agents (MCP)

This Actor is available through the Apify MCP server, so an AI agent can call it as a tool. Point your agent at `https://mcp.apify.com` and it can run the Packagist Scraper on demand — for example: *"Pull the first 500 packages from Packagist and summarise what you find."* The agent receives the same structured rows you would get from the UI.

### FAQ

#### Do I need a Packagist account or API key?

No. The Actor reads publicly available data only. There is nothing to authenticate and no credentials to rotate.

#### How many packages can I get in one run?

As many as the source exposes. Raise the page limit and **Max items** together; the run stops at whichever limit it reaches first.

#### Why did I get fewer rows than I asked for?

The source ran out of packages. That is normal for narrow searches — broaden the query or add more targets to one run.

#### Are results de-duplicated?

Yes. Each package is emitted once per run, even when it appears on several pages, so you are never billed twice for the same record.

#### Why are some fields empty?

Packagist does not publish every attribute for every package. Empty means the source did not supply it, not that extraction failed.

#### What export formats are supported?

JSON, CSV, Excel, HTML and RSS from the **Output** tab, plus the Apify API and any integration you connect.

#### How fast is it?

It is pure HTTP with no browser, so a page of results typically takes a second or two. Raise **Max concurrency** carefully — the source rate-limits aggressive crawling.

#### Can I schedule it?

Yes. Use the Apify scheduler to run it on any interval and append each run to the same dataset for time-series analysis.

#### Does it work behind a proxy?

It uses Apify Proxy automatically. You can switch groups or supply your own proxies in **Proxy configuration**.

#### How often does the data change?

Packagist updates continuously. Re-run whenever you need current data; the Actor always reads the live source, never a cache.

#### Is the output schema stable?

Yes. Field names and types are fixed, so downstream pipelines will not break between runs.

#### What if the source changes its format?

Open an issue on the **Issues** tab and it gets fixed. The Actor is actively maintained.

### Is it legal?

This Actor reads only publicly available data from Packagist — the same content any visitor or client sees without logging in. It does not bypass authentication, does not collect private data and does not attempt to defeat access controls. You are responsible for how you use the output: respect the source's terms of service, applicable copyright, and data-protection law such as GDPR where personal data is involved. Scraping public data is generally lawful in the EU and the US, but the responsibility for the downstream use of that data sits with you.

### Related scrapers

- [npm Package Intelligence](https://apify.com/logiover/npm-package-intelligence-scraper) — JavaScript registry
- [PyPI Package Scraper](https://apify.com/logiover/pypi-package-scraper) — Python registry
- [crates.io Scraper](https://apify.com/logiover/crates-io-scraper) — Rust registry
- [WordPress Plugin Scraper](https://apify.com/logiover/wordpress-plugin-directory-scraper) — PHP-adjacent ecosystem

# Actor input Schema

## `searchTerms` (type: `array`):

Terms to search Packagist for, e.g. logging, orm. Leave empty to walk the registry by package type.

## `packageType` (type: `string`):

Composer type used when no search term is given. Library covers the bulk of the registry.

## `tag` (type: `string`):

Narrow to a Packagist tag such as logging, testing or http.

## `includeDetails` (type: `boolean`):

Fetch stars, language, maintainers and release history for each package. Adds roughly a third of a second per package, so it decides how long a run takes.

## `maxPagesPerSearch` (type: `integer`):

How many result pages to walk for each search. Set 0 for no limit.

## `maxItems` (type: `integer`):

Stop after this many packages. Set 0 for no limit.

## `maxConcurrency` (type: `integer`):

Parallel requests. Lower this if the source rate-limits you.

## `proxyConfiguration` (type: `object`):

Proxy used to fetch pages. Defaults to Apify Proxy (automatic). You usually do not need to change this.

## Actor input object example

```json
{
  "searchTerms": [],
  "packageType": "library",
  "tag": "",
  "includeDetails": true,
  "maxPagesPerSearch": 3,
  "maxItems": 300,
  "maxConcurrency": 2,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All packages extracted in this run.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxPagesPerSearch": 3,
    "maxItems": 300,
    "maxConcurrency": 2
};

// Run the Actor and wait for it to finish
const run = await client.actor("logiover/packagist-php-package-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "maxPagesPerSearch": 3,
    "maxItems": 300,
    "maxConcurrency": 2,
}

# Run the Actor and wait for it to finish
run = client.actor("logiover/packagist-php-package-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxPagesPerSearch": 3,
  "maxItems": 300,
  "maxConcurrency": 2
}' |
apify call logiover/packagist-php-package-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,logiover/packagist-php-package-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/DfM0ZlaVZAHnxYjj7/builds/unfYoHQRHgxEudQER/openapi.json