🎯 GitHub Repo Audience Scraper

Export the developers who forked, watch, or contributed to any repository — as an enriched lead list.

Pick any GitHub repository — including your competitors' — and this Actor exports the developers actively engaged with it: the people who forked it, who watch it, and who contributed to it. Each is enriched with name, bio, company, location, website, X/Twitter and follower count. These are the highest-intent developer audiences on GitHub.

🔓 No token needed to start. Forkers and contributors work right away. Add a free GitHub token only to also collect watchers and to speed up very large jobs.

---

✨ Why you'll love it

• 🎯 The highest-intent developers — forking, watching and contributing are far stronger signals than a passive star.
• 🍴 Forkers = buyers — a developer who forked a repo is actively building with that technology.
• 🧑‍💻 Real profiles — name, company, location, website, X/Twitter and follower count in every row.
• 🏷️ Engagement tags — see exactly how each developer engaged (forker, watcher, contributor — or several at once).
• ⚔️ Competitor mining — export the audience of a rival project and reach developers already invested in your category.
• ⚡ Fast & scalable — profiles are fetched in efficient batches; handles very large repositories.

---

👥 Who it's for

You are…	Use it to…
🛠️ Dev-tool / SaaS marketer	Reach the developers building on a competing or complementary project.
🧲 Technical recruiter	Find engineers who use a specific technology, by company and location.
🚀 Founder / DevRel	Understand and re-engage the developers around your project.
📊 Market researcher	Map the active community of any framework, library or tool.
🤝 Agency / consultancy	Build targeted outreach lists of engineers in a niche.

---

🔑 Optional: add a token for watchers & speed (30 seconds)

Forkers and contributors work with no token at all. A free GitHub token unlocks the watchers audience and speeds up very large jobs:

1. Open github.com/settings/tokens → Generate new token → Tokens (classic).
2. For public repositories you don't need to tick any scope. (Optional: tick user:email to also collect public emails.)
3. Copy the token and paste it into the GitHub token field of this Actor.

Your token is stored securely and only used for your own runs.

---

⚡ Quick start

1. Open the Actor.
2. In GitHub repositories, type one or more repos as owner/repo or paste a URL — e.g. facebook/react, https://github.com/vercel/next.js.
3. Choose which audience types you want (forkers and contributors need no token; watchers need one).
4. Press Start — no token needed to begin.
5. Open the Output tab to preview, then Export → Excel / CSV / JSON, or send to Google Sheets, Airtable, Zapier, Make, or your app via API.

---

🧩 Input options

⭐ GitHub repositories · repos

The repositories whose audience you want. Enter as owner/repo (facebook/react) or paste a repo URL. Add as many as you like.

🏷️ Audience types · audienceTypes

Any combination of:

• 🍴 Forkers — developers who forked the repo (highest intent).
• 👀 Watchers — developers watching the repo's activity.
• 🛠️ Contributors — developers who committed to the repo.

🔑 GitHub token · githubToken (optional)

Not needed for forkers and contributors. Add a free personal access token to also collect watchers and to speed up large jobs — see the section above.

🔢 Max developers (total) · maxItems

Stop after this many developers in total. Defaults to 100. Set 0 for no limit.

🔢 Max developers per repository · maxPerRepo

Optional cap per repo — handy when scraping several repos at once. 0 = no per-repo cap.

✨ Enrich developer profiles · enrichProfiles

On by default. Collects full details for every developer. Turn off for a faster username-only list.

---

🧪 Example inputs

---

📤 Output

Every developer is one flat, spreadsheet-ready row. Only the fields that exist for a given profile are included, so your export stays clean.

📋 Field reference

Field	📖 Description
username	🧑‍💻 The developer's GitHub username.
name	Their display name.
bio	Profile bio.
company	🏢 Company / organization (often an @handle).
location	📍 Location.
websiteUrl	🔗 Personal or company website.
email	✉️ Public email — when available and the user:email scope is granted.
twitter	🐦 X / Twitter handle.
followersCount	👥 How many followers they have (influence signal).
followingCount	How many accounts they follow.
hireable	✅ Whether they flagged themselves open to work.
avatarUrl	🖼️ Avatar image.
profileUrl	🔗 Link to their GitHub profile.
type	User or Organization.
repo	⭐ The repository they engaged with.
engagements	🏷️ How they engaged — forker, watcher, contributor, or a combination.

🧑‍💻 Sample row

{
  "username": "shadowspawn",
  "name": "John Gee",
  "company": "@ExampleCorp",
  "location": "Auckland, New Zealand",
  "websiteUrl": "https://johngee.dev",
  "twitter": "shadowspawn",
  "followersCount": 210,
  "profileUrl": "https://github.com/shadowspawn",
  "type": "User",
  "repo": "tj/commander.js",
  "engagements": "contributor,watcher"
}

---

💡 Use cases in detail

🍴 Reach developers building on your category Export the forkers of a competing library. A fork means "I'm building with this" — the strongest possible signal of purchase intent for a developer tool.

🧲 Technology-specific recruiting The audience of a framework or library is full of engineers who use that technology. Filter by company and location to source candidates with exactly the right skills.

🚀 Re-engage your own community Scrape your repo's forkers, watchers and contributors to understand and reach the developers already invested in your project.

📊 Category & competitor mapping Combine several repos in a space, dedupe, and analyze the whole engaged developer community by company and geography.

---

🧠 Tips for best results

• 🍴 Forkers are the strongest leads — run forkers-only for the highest-intent list.
• 🏷️ Watch the engagements field — developers tagged with several engagements are your most invested audience.
• 🔢 Use a per-repo cap when comparing several big repos so results stay balanced.
• ⚡ Turn off enrichment for a quick username-only list, then enrich the ones you care about.
• 🧹 Deduplication is automatic within each repo.

---

🔌 Export & integrations

⬇️ Excel · CSV · JSON · XML · 📊 Google Sheets & Airtable · 🔔 Webhooks & API · 🤖 Make, Zapier, n8n

---

❓ FAQ

Do I need a token? — No. Forkers and contributors work with no token. A free token (no special scopes) additionally unlocks the watchers audience and speeds up very large jobs.

Is my token safe? — Yes. It's stored securely as a secret input and used only for your own runs.

What's the difference between the engagement types? — Forkers copied the repo to build with it, watchers subscribed to its activity, and contributors committed code to it. A developer can be more than one.

Are emails included? — Public emails are collected when you grant the optional user:email scope on your token and the developer has made their email public.

How many developers can I get per repo? — Up to a high practical limit per repository. Use the caps to control size and speed.

Will I get duplicates? — No. Developers are deduplicated within each repo, and multiple engagements are merged into one row.

Can I schedule it? — Yes. Use Apify Schedules to refresh your lists daily, weekly or monthly.

---

⚖️ Legal & responsible use

This Actor collects only publicly available profile information for legitimate research, recruiting and lead generation. You are responsible for how you use the data, including compliance with applicable laws (such as GDPR and CCPA), platform terms, and anti-spam rules when contacting anyone. Do not use the data for unsolicited bulk messaging or any unlawful purpose, and always respect the privacy and preferences of the people in your results.