Github Stars Email Extractor avatar

Github Stars Email Extractor

Pricing

from $14.99 / 1,000 results

Go to Apify Store
Github Stars Email Extractor

Github Stars Email Extractor

Extract a list of stargazer profile records from a Github repo URL. Includes email, user name, first name, location, company, and website.

Pricing

from $14.99 / 1,000 results

Rating

0.0

(0)

Developer

Alex

Alex

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

9 days ago

Last modified

Share

GitHub Stargazer Data Extractor

Extract accurate profile data from GitHub stargazers (users that star a repository).

Given a repo URL, the actor returns a list of records like this one:

{
"login": "username",
"email": "user@example.com",
"name": "Full Name",
"location": "San Francisco, CA",
"company": "Acme Inc",
"blog": "https://example.com",
"twitter": "handle",
"followers": 120,
"public_repos": 34,
"profile_url": "https://github.com/username",
"email_found": true
}

Features

  • High Accuracy: Only returns emails from actual stargazers (not random contributors)
  • Fast Processing: Concurrent extraction with intelligent rate limiting
  • Token Rotation: Support for multiple GitHub tokens for higher throughput
  • Proven Results: 92.8% average hit rate across major repositories

Input

Using this actor requires a Github account, as you need to provide at least one Personal Access Token with 'public_repo_access'.

This results in faster, more reliable results.

Input fields:

FieldRequiredDescription
repoYesFull GitHub repository URL
tokensYesArray of GitHub Personal Access Tokens (PAT) with public_repo scope
max_stargazersNoLimit number of stargazers to process (0 or empty = unlimited)

How to get your Github Personal Access Token

  1. Go to GitHub Settings → Tokens
  2. Click "Generate new token (classic)"
  3. Select public_repo scope
  4. Copy the token (starts with ghp_)
  5. Add to the tokens array

Output

Each stargazer record may include:

{
"login": "username",
"email": "user@example.com",
"name": "Full Name",
"location": "San Francisco, CA",
"company": "Acme Inc",
"blog": "https://example.com",
"twitter": "handle",
"followers": 120,
"public_repos": 34,
"profile_url": "https://github.com/username",
"email_found": true
}
  • email_found: true if email was found, false otherwise

Some fields can be undefined because some users keep them private.

Benchmark Results (800 stargazers tested across 8 repositories)

Overall Hit Rate: 92.8% (742/800 emails found)

RepositoryStargazersEmails FoundHit Rate
torvalds/linux1009898.0%
rust-lang/rust1009898.0%
facebook/react1009696.0%
nodejs/node1009595.0%
golang/go1009292.0%
microsoft/vscode1009191.0%
tensorflow/tensorflow1009090.0%
openclaw/openclaw1008282.0%

Speed Metrics (with 1 token)

  • Average: ~15.7 seconds per 100 stargazers
  • Throughput: ~380 stargazers per minute
  • Range: 13-21 seconds (depending on repository characteristics)

Use Cases

  • Developer outreach campaigns
  • Building email lists for product launches
  • Research on open source contributors
  • Community engagement

Notes

  • Only processes public repositories
  • Respects GitHub rate limits automatically
  • Filters out noreply@github.com addresses
  • Optimized for speed and accuracy