GitHub Trending Scraper - Daily Repos, Stars & Momentum
Pricing
Pay per usage
GitHub Trending Scraper - Daily Repos, Stars & Momentum
Get today's trending GitHub repositories as structured rows: owner, stars, forks, stars gained in the period, and language. GitHub publishes no API for its trending page and keeps no history, so run this daily and diff the results to track momentum.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
the anh nguyen
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Share
GitHub Trending Scraper
Today's trending GitHub repositories as structured rows — owner, stars, forks, stars gained in the period, and language — ready for a spreadsheet or a database.
GitHub publishes its trending page as HTML only. There is no API for it, and the page is rebuilt every day, so if you want the history you have to capture it yourself. This Actor turns each snapshot into clean records.
Input
| Field | Default | What it does |
|---|---|---|
since | daily | Trending window: daily, weekly or monthly |
spokenLanguage | en | GitHub's spoken-language filter for repo docs |
maxResults | 25 | Rows to return; the page lists about 25 per window |
Output
One row per repository:
| Field | Type | Example |
|---|---|---|
owner | string | PostHog |
repoName | string | posthog |
name | string | PostHog/posthog |
url | string | https://github.com/PostHog/posthog |
description | string | repo tagline as shown on the trending page |
language | string | Python |
stars | integer | 37927 — total stars |
forks | integer | 3211 |
periodStars | integer | 100 — stars gained during the window |
score | integer | rank score, highest first |
scrapedAt | string | ISO 8601 timestamp of capture |
periodStars is the field worth sorting on: total stars mostly measure age,
while stars gained this week measure momentum.
What it is good for
- Tracking momentum — run it daily and diff the results; a repo that appears three days running is a different signal from one that spikes once.
- Market and competitor watching — new entrants in your category usually show up here before they show up anywhere else.
- Dataset building — a daily snapshot compounds into a history nobody else has, because GitHub does not keep one.
Notes and limits
- The trending page is generated by GitHub and can differ between requests and regions. Treat a single run as a sample of that moment, not as a ranking of record.
- Only what the page shows is returned. Repository metadata beyond the trending card (issues, contributors, licence) needs the GitHub API.
- No authentication is required and no personal data is collected — the output describes repositories and their owning accounts as published publicly.
