GitHub Trending Repositories Scraper is a BrowserAct Bot template for collecting structured records from public GitHub Trending pages. Configure the language, time window, and result count, then run the Bot to return trending repository data for open-source research, developer ecosystem monitoring, competitive analysis, or workflow automation.
What Does BrowserAct GitHub Trending Repositories Scraper Do?
This template opens a public GitHub Trending page, reads each repository card, and returns one structured record per trending repository.
Key Features
- Extract public GitHub Trending repositories without requiring a GitHub login.
- Capture rank, full name, owner, repository name, URL, description, primary language, stars, forks, period growth, built-by contributor URLs, and since period.
- Configure base URL, language, since period, and count.
- Support daily, weekly, and monthly trending windows.
- Return fewer records than
countwhen GitHub lists fewer repositories for the selected page.
What Data Can I Extract from GitHub Trending?
| Field | Description |
|---|---|
rank |
Repository position on the Trending page. |
full_name |
Repository full name, such as owner/repo. |
owner |
Repository owner. |
repo_name |
Repository name. |
repo_url |
Public GitHub repository URL. |
description |
Repository description. |
language |
Primary language shown by GitHub. |
stars |
Total stars shown on the page. |
forks |
Fork count shown on the page. |
stars_period |
Stars gained during the selected period. |
built_by |
Visible contributor profile URLs. |
since |
Trending period used for the run. |
How to Use GitHub Trending Repositories Scraper
- Click Run task.
- Choose a programming language from the GitHub-supported dropdown.
- Choose the
daily,weekly, ormonthlyperiod. - Set how many repository records to collect.
- Run the Bot and review the structured repository results.
Input Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
base_url |
Yes | https://github.com |
Base GitHub URL without a trailing path. |
language |
Yes | javascript |
Dropdown with all plus 814 programming-language slugs from GitHub Trending. |
since |
Yes | daily |
Dropdown for daily, weekly, or monthly. |
count |
Yes | 25 |
Maximum number of repository records to return. |
Example Output
The table below uses records preserved from the validated Bot run. Up to the first 5 records are shown, and long values are shortened in this documentation preview.
| rank | full_name | owner | repo_name | repo_url | description | language | stars | forks | stars_period | built_by | since |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | example/repository | example | repository | https://github.com/example/repository | Example trending repository description. | JavaScript | 65583 | 12728 | 193 | ["https://github.com/example"] | daily |
How Does it Work?
BrowserAct constructs a public GitHub Trending URL from base_url, language, and since, then opens the page in a live browser. The Bot reads each repository card, maps the repository identity, counts, language, growth text, and visible built-by contributor profile links, then returns records in page order.
GitHub Trending is a single public page and may list fewer repositories than the requested count. In that case, BrowserAct returns all available records and stops cleanly.
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 GitHub Trending Repositories?
GitHub Trending data helps teams monitor open-source momentum, discover fast-growing developer tools, track language ecosystems, compare repository traction, and route repository signals into dashboards or agents.
Who Can Use This Template?
- Developer relations teams tracking open-source trends.
- Product teams researching developer tools.
- Investors and analysts monitoring fast-growing repositories.
- Engineering teams discovering libraries and frameworks.
- Automation builders routing repository records into reports, alerts, databases, or agents.
How Many Results Can You Scrape?
Use count to control the maximum number of repositories returned. GitHub Trending is a single page, so the Bot returns all visible repositories when the page contains fewer than your requested count.
Automation and Export
BrowserAct returns structured GitHub repository 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
