GitHub Trending Scraper ⭐

foXLabs web & community series: Hacker News · Wikipedia companies · Community listening

🎉 Turn GitHub trending into clean, structured data — no login, no API key, one row per repository, with the name, owner, language, stars, description and today’s star gain. Built for developer-tool sales, VC scouting and tech research.

🔍 What is the GitHub Trending Scraper — and when should you use it?

Give this actor languages or timeframes and it returns matching repositories from GitHub trending repositories (public) — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

Use it when you need: trending repositories by language; rising projects to scout; or a daily/weekly trending feed.

Use something else when: you need full repo analytics — this is the trending listing, not the GitHub API’s full stats.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/github-trending-scraper.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull repository company records using the Apify Actor `foxlabs/github-trending-scraper`.
Input: `mode`, `languages`, `periods`, `spokenLanguage` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"mode":"trending","maxResults":200}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/github-trending-scraper.md.

📋 Overview

Everything you need to turn GitHub trending repositories (public) into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole feed, one call — name or ID in, matching repositories out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~github-trending-scraper/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"trending","maxResults":200}'

🚀 Getting Started (3 steps)

1. Choose your targets — languages or timeframes.
2. Set the cap — maxResults limits how many results are returned.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"mode":"trending","maxResults":200}

Field	Type	Description
mode	string	Trending repos = today's / this week's / this month's github.com/trending list (12-22 repos per page). Trending developers = the people list (25 per page).…
languages	array	Trending modes. GitHub language slugs, e.g. ["python", "rust", "typescript"]. Each language is a separate trending page. Leave empty for the all-languages page.
periods	array	Trending modes. Which trending window(s) to pull — daily, weekly and/or monthly. Every language is fetched for every period selected.
spokenLanguage	string	Trending modes, optional. Two-letter code to keep only repos written in a spoken language (e.g. "en", "zh", "es"). Leave empty for all.
minStars	integer	Discover mode. Only repos with at least this many stars. Lower it to catch earlier-stage projects, raise it for established ones.
dateField	string	Discover mode. Created = when the repo was first published (finds genuinely new projects). Pushed = last commit (finds actively maintained ones).
dateFrom	string	Discover mode. YYYY-MM-DD. Defaults to 90 days ago.
dateTo	string	Discover mode. YYYY-MM-DD. Defaults to today.
windowDays	integer	Discover mode. The period is sliced into windows of this many days and each window is searched separately — that's how the run gets past GitHub's…
discoverLanguage	string	Discover mode, optional. One language, e.g. "rust". Leave empty for all languages.
topic	string	Discover mode, optional. A GitHub topic, e.g. "llm", "kubernetes", "fintech". Leave empty for all topics.
searchQuery	string	Discover mode, optional. Raw GitHub search qualifiers appended to the query, e.g. "license:mit forks:>10". Leave empty unless you know the syntax.
enrichRepos	boolean	Adds what the trending page doesn't show: topics, license, homepage, created & last-push dates, open issues and watchers, from the official GitHub API. Discover…
enrichOwners	boolean	Adds each repo owner's (or developer's) public profile: name, company, blog, X handle, location, followers and e-mail where they made it public. One extra API…
githubToken	string	Without a token GitHub allows ~60 API requests/hour, so enrichment stops early on big runs (rows say so in enrichmentStatus — never silently empty). A free…
maxResults	integer	Hard cap on dataset rows. Set 0 for unlimited.

📤 Output

One row per result, saved to the dataset. Every row carries scrapedAt. Lookups that cannot be completed are reported in the run log rather than silently dropped.

Field	Description
rank	Rank
fullName	Full Name
owner	Owner
name	Name
url	Url
description	Description
language	Language
totalStars	Total Stars
totalForks	Total Forks
starsInPeriod	Stars In Period
builders	Builders
source	Source
topics	Topics
license	License
homepage	Homepage
openIssues	Open Issues
watchers	Watchers
isArchived	Is Archived
isFork	Is Fork
defaultBranch	Default Branch
createdAt	Created At
pushedAt	Pushed At
ownerType	Owner Type
ownerName	Owner Name
ownerCompany	Owner Company
ownerBlog	Owner Blog
ownerEmail	Owner Email
ownerTwitter	Owner Twitter
ownerLocation	Owner Location
ownerFollowers	Owner Followers
ownerPublicRepos	Owner Public Repos
ownerUrl	Owner Url
fetchedAt	Fetched At

💼 Use cases

1. Dev-tool scouting — find rising projects in a language. Input: languages. Output: repos + star gain. Use: a scouting list.

2. VC / M&A sourcing — spot fast-growing open-source projects. Input: timeframes. Output: trending repos. Use: a sourcing pipeline.

3. Tech trend research — track what’s trending by language. Input: languages, scheduled. Output: trending feed. Use: a trend report.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/github-trending-scraper').call({"mode":"trending","maxResults":200});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/github-trending-scraper').call(run_input={"mode":"trending","maxResults":200})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads GitHub trending repositories (public).

What do I search by? Languages or timeframes.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

What does each row cover? One trending repository: name, owner, language, total stars, description and the period’s star gain.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise maxResults, or refine the input.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor reads public GitHub trending listings. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.2.10 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"mode":"trending","maxResults":200}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.2 — 2026-09-07

• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from GitHub trending repositories (public) by name or registry ID.