Packagist PHP Package Search Scraper is a BrowserAct Bot template for collecting structured Composer package records from public Packagist search results. Configure a keyword and result count, then run the Bot to return ranked PHP package metadata for dependency research, ecosystem monitoring, package discovery, developer tooling, or automation workflows.
What Does BrowserAct Packagist PHP Package Search Scraper Do?
This template opens Packagist search for your keyword, extracts public package result cards, follows pagination when needed, and returns one structured record per Composer package.
Key Features
- Extract public Packagist search results without requiring a login.
- Capture rank, package name, package URL, vendor, description, download count, favorite count, optional visible metadata, and search keyword.
- Configure base URL, keyword, and count.
- Continue through Packagist result pages until the requested count is reached.
- Keep package metadata ready for dependency review, PHP ecosystem analysis, dashboards, and agent workflows.
What Data Can I Extract from Packagist?
| Field | Description |
|---|---|
rank |
Search result position. |
package_name |
Composer package name. |
package_url |
Public Packagist package URL. |
vendor_name |
Vendor namespace parsed from the package name. |
description |
Package description shown on the search card. |
download_count |
Download count shown by Packagist. |
favorite_count |
Favorite count shown by Packagist. |
last_updated |
Last updated time when visible. |
latest_version |
Latest version when visible. |
package_type |
Package type when visible. |
license |
License information when visible. |
search_keyword |
Keyword used for the run. |
How to Use Packagist PHP Package Search Scraper
- Click Run task.
- Enter the Packagist base URL.
- Enter a package, framework, library, or PHP ecosystem keyword.
- Set how many package records to collect.
- Run the Bot and review the structured Packagist package results.
- Reuse the Bot with another keyword or connect the output to your workflow.
Input Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
base_url |
Yes | https://packagist.org |
Packagist base URL without a trailing slash. |
keyword |
Yes | laravel |
Search keyword sent as the q parameter. |
count |
Yes | 20 |
Maximum number of package records to return. |
Example Output
{
"results": [
{
"rank": 1,
"package_name": "laravel/framework",
"package_url": "https://packagist.org/packages/laravel/framework",
"vendor_name": "laravel",
"description": "The Laravel Framework.",
"download_count": "564551216",
"favorite_count": "35360",
"last_updated": "",
"latest_version": "",
"package_type": "",
"license": "",
"search_keyword": "laravel"
}
]
}
How Does it Work?
BrowserAct constructs a public Packagist search URL from base_url and keyword, opens the search results page, waits for the public result cards to render, and reads each visible package card. The Bot maps each card into a ranked record with package name, URL, vendor, description, download count, favorite count, optional visible fields, and keyword.
When count is higher than the first result page, BrowserAct follows Packagist pagination using the public page parameter. The Bot stops when it reaches the requested count or when a page has no more public package result cards.
How to Build a New Scraper Bot with Agent Built
Step 1: Describe the Data You Need
Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Paste a clear request that includes the website, the records to collect, the filters or search conditions, the fields to return, the result limit, and the inputs you want to reuse later.
Step 2: Let BrowserAct Build and Test the Bot
BrowserAct explores the live website, works out the navigation and extraction path, and validates the result. If BrowserAct asks for clarification, reply in the same build conversation with the missing URL, condition, field, example, or expected output.
Step 3: Run the Bot and Review the Result
When the build is complete, run the Bot with the default inputs first. Review the structured records, source URLs, missing fields, and row count before reusing the Bot with new inputs or connecting it to another workflow.
Why Scrape Packagist Package Search Results?
Packagist search data helps teams discover Composer packages, compare PHP library popularity, monitor ecosystem activity, review package candidates, and route package metadata into developer reports, dependency dashboards, or agent workflows.
Who Can Use This Template?
- PHP developers researching libraries and alternatives.
- Laravel teams discovering packages around a framework or use case.
- Developer tooling teams building package discovery workflows.
- Security and dependency teams reviewing public package metadata.
- Automation builders routing package data into spreadsheets, databases, alerts, or agents.
How Many Results Can You Scrape?
Use count to control the number of Packagist package records returned. Packagist typically shows 20 results per page, and BrowserAct follows pagination until the requested count is reached or no more public results are available.
Automation and Export
BrowserAct returns structured Packagist package records first. You can then use the output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual CSV review.
Need Help?
Contact us at
Discord: Discord Community
E-mail: service@browseract.com
