GitHub Trending Repos

Pull the GitHub Trending list (daily, weekly, or monthly) by programming language and spoken language. One row per repo with owner, description, language, total stars, stars gained in the period, sample contributors. No auth.

What you get

{
  "snapshotAt":            "2026-06-03T07:55:11+00:00",
  "period":                "daily",
  "languageFilter":        "python",
  "spokenLanguageFilter":  null,
  "rank":                  1,
  "owner":                 "microsoft",
  "repo":                  "markitdown",
  "fullName":              "microsoft/markitdown",
  "url":                   "https://github.com/microsoft/markitdown",
  "description":           "Python tool for converting files and office documents to Markdown.",
  "programmingLanguage":   "Python",
  "languageColor":         "#3572A5",
  "stars":                 53241,
  "forks":                 2710,
  "starsInPeriod":         1265,
  "contributorsSample":    ["afourney", "gagb", "sugatoray"]
}

How to use

Input.

{
  "periods":         ["daily", "weekly", "monthly"],
  "languages":       ["python", "rust", "typescript"],
  "spokenLanguages": ["en"]
}

periods: daily, weekly, or monthly. Empty = daily.

languages: GitHub language slugs. Common: python, typescript, javascript, rust, go, c++, c%23 (C#), unknown. Empty = all languages.

spokenLanguages: ISO 639-1 codes for README spoken language. Useful to filter out non-English-readme noise. Empty = all.

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
GitHub Trending repo entry	$1.00	$0.90	$0.80	$0.70

Bronze, Silver and Gold are the discounts Apify gives users of its paid plans. The Pricing tab always shows the current prices.

Buyer

• Dev-tool marketers tracking competing OSS launches.
• VC associates watching "what's heating up on GitHub this week".
• Newsletter writers building a Monday digest.
• Hiring teams sourcing engineers who are launching popular OSS.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/github-trending-repos").call(run_input={})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/github-trending-repos').call({});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~github-trending-repos/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/github-trending-repos",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account, cookies or an API key?

No. The actor reads public data without logging in. You only need an Apify account to start it.

How am I charged?

Pay per event, at the prices on the Pricing tab for your Apify plan (the Pricing section of this page lists them). The platform usage of the run is included in those prices, and your spending limit for a run is always respected.

Why did my run return no results?

The status message and the log of the run say why: usually nothing matched the input, or the source did not answer for a moment. Check the input against the example above and run it again.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects data that the source publishes openly, without a login. Public data can still be personal data under laws such as the GDPR, and sources have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the source changes?

An automated test runs the actor every day on the example input and checks the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• npm Package Stats Scraper: Metadata and Downloads
• GitHub Security Advisories Scraper by Ecosystem
• NVD CVE Scraper: Vulnerabilities by Vendor and Severity
• Product Hunt Scraper: Daily Launches
• Hacker News Scraper: Stories and Comments by Query
• App Store Scraper: App Details, Ratings, Prices

Source

https://github.com/trending: GitHub's server-rendered trending page. No auth, no rate-limit headers (GitHub is generous for HTML). Actor paces 0.6 s between pages.