GitHub Trending Repos Scraper β€” Daily, Weekly, Monthly avatar

GitHub Trending Repos Scraper β€” Daily, Weekly, Monthly

Pricing

from $2.00 / 1,000 results

Go to Apify Store
GitHub Trending Repos Scraper β€” Daily, Weekly, Monthly

GitHub Trending Repos Scraper β€” Daily, Weekly, Monthly

Scrape github.com/trending for top repositories β€” daily, weekly, or monthly. Filter by programming language. Get repo name, owner, description, language, stars, forks, builders. Ideal for dev intelligence, AI/ML trend tracking, VC sourcing, and developer marketing.

Pricing

from $2.00 / 1,000 results

Rating

0.0

(0)

Developer

Berkan Kaplan

Berkan Kaplan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 days ago

Last modified

Categories

Share

GitHub Trending Scraper ⭐

πŸŽ‰ 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.

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 queries the source live, so the data is as fresh as the registry itself.

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: `queries` is a list of languages or timeframes. `maxResultsPerQuery` caps rows per query.
Start with: {"queries":["undefined"],"maxResultsPerQuery":50}
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.
  • πŸ’° Pay only for results β€” per-row pricing, empty/failed lookups never billed.
  • πŸ€– 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 '{"queries":["undefined"],"maxResultsPerQuery":50}'

πŸš€ Getting Started (3 steps)

  1. Choose your targets β€” languages or timeframes.
  2. Set the cap β€” maxResultsPerQuery limits rows per query.
  3. Run and export β€” get a clean dataset as JSON, CSV or Excel.

πŸ“₯ Input

{"queries":["undefined"],"maxResultsPerQuery":50}
FieldTypeDescription
queriesarrayLanguages or timeframes.
maxResultsPerQueryintegerCaps rows per query.
maxConcurrencyintegerHow many queries to fetch at once.
includeRawbooleanAttach the source’s untouched record under raw.

πŸ“€ Output

One row per company, saved to the dataset. Every row also carries query, scrapedAt, and β€” when a lookup fails β€” an error explaining why (never silently dropped, never billed).

FieldDescription
rankRank
fullNameFull Name
ownerOwner
nameName
urlUrl
descriptionDescription
languageLanguage
totalStarsTotal Stars
totalForksTotal Forks
starsInPeriodStars In Period
buildersBuilders
sourceSource
topicsTopics
licenseLicense
homepageHomepage
openIssuesOpen Issues
watchersWatchers
isArchivedIs Archived
isForkIs Fork
defaultBranchDefault Branch
createdAtCreated At
pushedAtPushed At
ownerTypeOwner Type
ownerNameOwner Name
ownerCompanyOwner Company
ownerBlogOwner Blog
ownerEmailOwner Email
ownerTwitterOwner Twitter
ownerLocationOwner Location
ownerFollowersOwner Followers
ownerPublicReposOwner Public Repos
ownerUrlOwner Url
fetchedAtFetched 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({"queries":["undefined"],"maxResultsPerQuery":50});
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={"queries":["undefined"],"maxResultsPerQuery":50})
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 queries β†’ 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 maxResultsPerQuery, or refine the name.
  • 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.

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

Changelog

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.