GitHub Intel: Repos, Developer Leads & Stargazer Lists

Pricing

Rating

Developer

Actor stats

Categories

Share

Turn GitHub into structured, B2B-ready data. Three modes in one actor, built on the official GitHub REST API. No proxy, no scraping of HTML, no breakage.

Bring your own read-only GitHub token (optional but recommended): it lifts the rate limit from 60 to 5000 requests per hour. No special scopes are needed for public data.

What it does

1. Repositories (intel)

Search repositories by language, topic, minimum stars, or creation date. Every result is a clean row:

• fullName, owner, ownerType, description
• language, topics, license, homepage
• stars, forks, watchers, openIssues
• createdAt, updatedAt, pushedAt, url

Use it for competitive intel, ecosystem mapping, or finding fast-growing projects in your space.

2. Developer leads (users)

Find developers by location, language, and minFollowers. With enrichProfiles on, each result is a full lead:

• login, name, company, location
• email and blog (when public), twitter
• bio, hireable, publicRepos, followers
• url

Ideal for dev recruiting and developer-tooling sales.

3. Stargazers / contributors of a repo

Export the people behind a repository as enriched leads. Point it at any repo (owner/name) and choose leadSource: stargazers (warm, interested in the space) or contributors. Each lead is enriched with the same profile fields as mode 2, plus sourceRepo, starredAt, and contributions where available.

This is the highest-intent lead list on GitHub: the people who starred your competitor already care about the problem you solve.

Delta / monitor mode

Set deltaMode: true to only emit items new since the previous run. State is stored per Apify account.

• Repos: repositories with new activity (a push) since the last run.
• Stargazers: it resumes from where the last run stopped, so the same stargazers are never pulled twice.

Pair it with a schedule and a webhook for recurring alerts on active projects or fresh leads. This is recurring usage, not a one-shot scrape.

Example inputs

Fast-growing Rust repositories created this year:

{"mode":"repos","language":"Rust","minStars":100,"createdAfter":"2026-01-01","sort":"stars"}

Swift developers in Brussels with a following:

{"mode":"users","language":"Swift","location":"Brussels","minFollowers":50,"enrichProfiles":true}

Enriched leads from a competitor's stargazers, only new stars each run:

{"mode":"stargazers","repo":"owner/their-product","enrichProfiles":true,"deltaMode":true}

Who uses this

• Recruiters and sourcers building structured developer pipelines
• Developer-tooling and SaaS teams running competitive and ecosystem intel
• Sales teams turning stargazers and contributors into warm leads

Founder / VC / Sales data suite

Part of a B2B data suite. Pair with our other actors for full coverage:

• Hacker News Intel (Who is hiring jobs, Show HN launches, keyword monitor)
• Y Combinator Companies Scraper (startups by batch, industry, region)
• IndieHackers Product Scraper (products, revenue, founders)
• BetaList Startup Scraper (upcoming launches and makers)

Notes

• Search modes return up to 1000 results (a GitHub API limit). Narrow your query for full coverage of a large space.
• The actor respects GitHub rate limits and waits for resets automatically. Providing a token avoids almost all waiting.
• Only public data is returned. Email and company appear only when the user has made them public.