GitHub Profile Scraper & Lead Finder | Stars, LinkedIn, Score avatar

GitHub Profile Scraper & Lead Finder | Stars, LinkedIn, Score

Pricing

from $1.90 / 1,000 results

Go to Apify Store
GitHub Profile Scraper & Lead Finder | Stars, LinkedIn, Score

GitHub Profile Scraper & Lead Finder | Stars, LinkedIn, Score

Scrape GitHub profiles via the official API, or pull every stargazer/forker of a repo as warm leads. Get email, LinkedIn & social accounts, repos, stars, top languages, orgs, README — plus a 0-100 lead score, developer tier & outreach icebreaker. CSV export. $1.9/1K.

Pricing

from $1.90 / 1,000 results

Rating

0.0

(0)

Developer

Apivault Labs

Apivault Labs

Maintained by Community

Actor stats

0

Bookmarked

23

Total users

8

Monthly active users

4 days ago

Last modified

Share

🐙 GitHub Profile Scraper & Lead Finder

Scrape any public GitHub profile via GitHub's official API — or paste a repository URL and pull every stargazer / forker as a ready-to-use lead list. Returns identity, email, LinkedIn & all social accounts, repositories, total stars, languages, organizations and the profile README — then layers on a 0-100 lead score, developer tier and a ready-to-send outreach icebreaker.

Built for recruiters, B2B sales, devtool marketers and OSS researchers. No browser, official API, only successful results are billed.

Two modes

1. Profile mode — usernames in, enriched profiles out

Paste usernames or https://github.com/NAME URLs. Get the full profile + intelligence layer.

2. Lead mode — repo in, developer leads out ⭐

Paste a repository URL (https://github.com/OWNER/REPO). The actor pulls every developer who starred (or forked) that repo and hydrates each into a complete lead profile with a lead score.

"Find every developer who starred my competitor's repo" — turn any popular repository into a warm B2B prospect list. Filter by lead score, followers, stars, hireable status or public email.

What makes this the most complete GitHub actor

CapabilityThis actorTypical competitor
Official GitHub API (live, accurate)Some HTML-scrape (fragile)
Email (public)Sometimes
LinkedIn + all social accountsRarely
Repo aggregates (stars, forks, top languages)Sometimes
Full repo list (topics, license, issues, forks)Rarely
Bytes-weighted language %
Organizations, starred repos, profile READMERarely
Achievement badges + highlightsSome
Pinned repos (enriched)Some
Contributions in the last yearSome
Stargazer / forker lead extractionRarely
0-100 lead score + tier + reasons
Outreach icebreaker + best contact
Filters (followers / stars / score / hireable / email)
Proxy IP rotation (beats 60 req/h limit)Often none
Per-user fault isolation (one error ≠ dead batch)Often batch-halting
CSV / JSON exportVaries

Input

{
"profileUrls": ["https://github.com/sindresorhus", "torvalds"],
"repoUrls": ["https://github.com/apify/crawlee"],
"repoLeadsSource": "stargazers",
"maxLeadsPerRepo": 50,
"extractRepos": true,
"includeRepoList": false,
"includeLanguageStats": false,
"includeSocialAccounts": true,
"includeOrganizations": false,
"includeStarred": false,
"includeReadme": false,
"includeAchievements": false,
"includePinnedRepos": false,
"includeContributions": false,
"minLeadScore": 0,
"withEmailOnly": false,
"exportFormat": "default"
}

Use profileUrls, repoUrls, or both. Every option is independent.

Output (abridged)

{
"success": true,
"username": "sindresorhus",
"fullName": "Sindre Sorhus",
"bio": "Full-Time Open-Sourcerer",
"company": "",
"location": "",
"email": "",
"website": "https://sindresorhus.com",
"twitterUsername": "sindresorhus",
"linkedin": "",
"profileUrl": "https://github.com/sindresorhus",
"followers": 78000,
"following": 31,
"publicRepos": 1133,
"accountCreated": "2011-02-15",
"accountAgeYears": 15.1,
"accountAgeTier": "veteran",
"developerTier": "mega",
"activityStatus": "active",
"isInfluencer": true,
"hireable": false,
"totalStars": 784000,
"totalForks": 41000,
"topLanguages": ["JavaScript", "TypeScript", "Swift"],
"mostStarredRepo": { "name": "awesome", "stars": 320000, "url": "..." },
"socialAccounts": [{ "provider": "twitter", "url": "..." }],
"leadScore": 74,
"leadTier": "hot",
"leadReasons": ["78,000 followers (mega)", "784,000 stars", "veteran account (15.1y)"],
"bestContact": { "channel": "website", "value": "https://sindresorhus.com" },
"outreachIcebreaker": "Hi Sindre Sorhus — with 15.1+ years on GitHub, 78,000 followers and 784,000 stars, your open-source work really stands out."
}

In lead mode each record also carries leadSource: { "type": "stargazers", "repo": "apify/crawlee" }.

Enable includeRepoList, includeLanguageStats, includeOrganizations, includeStarred, includeReadme, includeAchievements, includePinnedRepos or includeContributions to add those sections.

Lead score

A transparent 0-100 score (with human-readable leadReasons) computed from followers, total stars, public repos, account age, public email, LinkedIn, company and hireable status. Tiers: cold / warm / hot / scorching. Sort or filter on it to surface the best prospects first.

Pricing

  • $0.0019 per profile ($1.9 per 1,000) — pay per result, no subscription.
  • A failed / not-found / private lookup is never charged.
  • In lead mode you pay one profile lookup per stargazer/forker hydrated.

Rate limits & token

GitHub allows ~60 requests/hour per IP unauthenticated; the actor rotates Apify proxy IPs to spread load. For large batches or lead mode, add an optional read-only GitHub token to raise the limit to 5000/hour. No scopes needed.

Use cases

  • Recruiting — find hireable developers with public emails, filter by language and activity.
  • B2B / devtool sales — extract stargazers of a competitor's repo as warm leads, scored and ready for outreach.
  • OSS community growth — identify influential users who starred your project.
  • Market & competitor research — map a company's engineers, their stacks and orgs.
  • CRM enrichment — append GitHub + LinkedIn data to existing contacts.

Notes

  • Only publicly available data is extracted. email and linkedin appear only when the user has set them public.
  • totalStars / totalForks are aggregated over the sampled repos (cap maxRepos, GitHub page ceiling 100).
  • languageStats percentages are bytes-weighted from GitHub's per-repo language endpoint (top repos).

Disclaimer

Extracts only publicly available data. Ensure your use complies with applicable laws, GDPR/CCPA and GitHub's terms of service. Not affiliated with GitHub, Inc.