GitHub Repository Scraper - Stars, Forks, Topics & Activity
Pricing
from $0.20 / 1,000 results
GitHub Repository Scraper - Stars, Forks, Topics & Activity
Scrape GitHub repositories by any search query. Stars, forks, language, topics, license and activity dates as JSON or CSV.
Pricing
from $0.20 / 1,000 results
Rating
0.0
(0)
Developer
Dominik
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Extract GitHub repositories matching any search query, with stars, forks, topics, licence and activity dates.
What you can do with it
- Developer lead generation - find maintainers and companies building in your space.
- Technology trend research - track adoption by language, topic or star growth.
- Competitive intelligence - monitor a competitor's public repos and release cadence.
- Dependency and licence auditing - pull licence data across many repos at once.
- Feed an AI agent - structured repo metadata with no HTML parsing.
Input
Every field is optional. Run it with no configuration and it returns useful data straight away.
| Field | Type | Description |
|---|---|---|
search | string | GitHub search syntax, e.g. 'stars:>1000 language:python' or 'topic:machine-learning pushed:>2026-01-01'. |
sort | string | One of: stars, forks, updated. Default stars. |
maxItems | integer | How many repos to return. GitHub caps any search at 1000 results. Default 200. |
token | string | Anonymous access is limited to 60 requests/hour. A personal access token raises this to 5,000/hour. Leave empty for small runs. |
Output
Flat JSON records, exportable as JSON, CSV, Excel or XML. Fields the source does
not publish come back as null rather than being omitted, so your schema stays
stable between runs.
Pricing
Pay per result. You are charged only for records actually delivered - a run that matches nothing costs nothing.
Keeping it fresh
Use Apify Schedules to run this on a timer and your dataset stays current without you touching it. Add a webhook to push new records straight into your database, Google Sheet or Slack channel.
Reliability
This reads the source's own public API - no logins, no bot circumvention. That is a deliberate choice: actors that depend on defeating bot protection break without warning. This one does not.