GitHub Profile Scraper & Lead Finder

Turn public GitHub profiles, repository audiences, and organization members into structured developer research records.

Collect identity and activity signals, compare public repositories and languages, qualify profiles with optional research scores, and export the results for recruiting, community analysis, or responsible B2B research.

Choose your workflow

Profile research

Provide GitHub usernames or profile URLs to collect structured public profile data.

Repository audience research

Provide repository URLs to discover available stargazers, forkers, or contributors and enrich each username into a profile record. The number of profiles returned depends on your configured limit and current data availability.

Organization research

Provide organization names or URLs to collect publicly listed members and compare their profile signals.

You can combine all three workflows in one run. Duplicate usernames are merged automatically.

Data you can collect

Category	Example fields
Identity	username, fullName, bio, company, location, profileUrl
Public contact	email, website, twitterUsername, linkedin, socialAccounts
Profile metrics	followers, following, publicRepos, accountAgeYears
Repository signals	totalStars, totalForks, topLanguages, mostStarredRepo
Optional sections	repositories, organizations, starred projects, profile README, pinned repositories, achievements, contributions
Research fields	developerTier, activityStatus, leadScore, leadTier, leadReasons
Audience source	repository, organization, and source type when using discovery modes

Only data available for the selected public profile and enabled options is returned. Missing contact or activity fields are not fabricated.

Quick start

Collect specific profiles

{
  "profileUrls": [
    "https://github.com/your-github-username",
    "another-username"
  ],
  "extractRepos": true,
  "includeSocialAccounts": true,
  "includeLeadScore": true
}

Research a repository audience

{
  "repoUrls": ["https://github.com/owner/repository"],
  "repoLeadsSource": "stargazers",
  "maxLeadsPerRepo": 100,
  "minLeadScore": 40
}

Research public organization members

{
  "orgUrls": ["example-organization"],
  "minFollowers": 10,
  "exportFormat": "csv"
}

Example output

This example is fictional and illustrates the typical structure. Actual fields vary by profile and selected options.

{
  "success": true,
  "username": "maya-chen-example",
  "fullName": "Maya Chen",
  "bio": "Software engineer building developer tools",
  "company": "Northstar Labs",
  "location": "Toronto, Canada",
  "followers": 3856,
  "following": 142,
  "publicRepos": 42,
  "accountAgeYears": 8.4,
  "developerTier": "established",
  "activityStatus": "active",
  "totalStars": 12734,
  "totalForks": 982,
  "topLanguages": ["Python", "TypeScript", "Go"],
  "mostStarredRepo": {
    "name": "signal-kit",
    "stars": 4210
  },
  "leadScore": 82,
  "leadTier": "hot",
  "leadReasons": [
    "strong public project signals",
    "active developer profile",
    "established account"
  ],
  "leadSource": {
    "type": "stargazers",
    "repo": "example-org/example-repo"
  }
}

Optional profile depth

Keep runs lightweight or enable only the sections you need:

• Repository aggregates and an optional full repository list.
• Language distribution across sampled public repositories.
• Public social accounts and organizations.
• A sample of starred repositories.
• Profile README and pinned repositories.
• Public achievements and recent contribution signals.
• Optional public contact discovery and basic email-domain checks.

Deeper options can require more requests and may reduce throughput. Start with the default profile fields, then enable additional sections for shortlisted profiles.

Understanding the research score

leadScore is an optional 0–100 prioritization aid based on available public profile and repository signals. leadReasons explains the high-level factors present in a result.

The score is not a measure of personal worth, job performance, identity, financial capacity, or legal eligibility. Do not use it as the sole basis for employment, credit, housing, insurance, education, or other high-impact decisions. Review relevant profiles manually and apply your own documented criteria.

Filters

Filter before saving results with:

• minLeadScore
• minFollowers
• minRepos
• minStars
• hireableOnly
• withEmailOnly

Filters depend on the corresponding field being available. For example, a stars filter requires repository aggregation.

Exports and automation

Results are saved to the run's Apify Dataset and can be downloaded as JSON, CSV, Excel, XML, or RSS. Use exportFormat: "csv" for a flatter row designed for spreadsheet and CRM workflows.

For n8n, use the community package n8n-nodes-apivault-github to start the Actor and pass dataset results to the next workflow step.

Pricing

The active result price is $0.0019 per successfully collected profile:

Successful profiles	Result charge
1	$0.0019
100	$0.19
1,000	$1.90
10,000	$19.00

Apify platform usage and a small Actor Start charge may apply according to the pricing shown before each run. Profiles excluded by filters or unsuccessful lookups are not billed as successful result events.

FAQ

Are email and LinkedIn guaranteed?

No. Contact fields are returned only when a public source exposes them. Many developers intentionally keep these fields private.

Can I collect every stargazer, forker, contributor, or organization member?

The Actor collects the available audience up to your configured limit. Results can vary because profiles may be private, removed, duplicated, unavailable, or excluded by filters.

Do I need a GitHub token?

Not for small public-profile runs. An optional read-only token can provide higher authorized request limits for larger workloads. Use the minimum permissions required and never paste credentials into logs or support messages.

What does totalStars mean?

It is aggregated across the public repositories included in the configured sample, not necessarily every repository ever associated with the account.

Can I use the results for outreach?

Use public contact information responsibly. Respect consent, opt-outs, applicable privacy and anti-spam laws, platform terms, and reasonable contact frequency. Avoid bulk unsolicited messaging.

Responsible use

• Collect only the fields needed for a legitimate purpose.
• Do not attempt to identify private individuals or infer sensitive traits.
• Do not use the output for harassment, surveillance, credential attacks, or automated spam.
• Secure exported contact data and delete it when no longer needed.
• Follow GitHub's terms and applicable privacy laws, including GDPR and CCPA where relevant.

Support

Open an issue on the Actor page with a sample input and run ID. Remove API tokens, cookies, private contact lists, and other secrets before sharing diagnostics.

GitHub is a trademark of GitHub, Inc. This Actor is an independent tool and is not affiliated with or endorsed by GitHub.