GitHub Repo and Org B2B Lead Intelligence

Find high-signal B2B leads from public GitHub repositories and organizations. This Actor searches GitHub repositories by topic, language, stars, and activity, then scores repos for developer-tool, security, AI, infrastructure, recruiting, and agency sales potential.

What it does

• Searches the public GitHub repository API using your chosen queries.
• Extracts repository, owner, language, stars, forks, open issues, topics, website, and activity timestamps.
• Optionally enriches organization-owned repos with public company name, domain, location, website, email, Twitter username, follower count, and organization age.
• Scores each repo from 0 to 100 using traction, recent activity, organization ownership, website presence, and B2B category signals.
• Scores each lead for contactability from 0 to 100 using public contact channels the GitHub profile already exposes, so you can sort a list by who is actually reachable instead of by stars alone.
• Filters out forks by default.
• Produces clean dataset rows for sales, recruiting, security, devtools, and investor workflows.

Best use cases

• Devtools companies finding prospects using relevant technologies.
• Security vendors finding active open-source projects and organizations.
• Recruiters discovering fast-moving engineering teams.
• Agencies identifying companies with active technical initiatives.
• Investors and analysts monitoring developer traction by category.

Example input

{
  "queries": [
    "topic:llm stars:>50 pushed:>2026-01-01",
    "topic:devtools stars:>100 pushed:>2026-01-01",
    "topic:security stars:>50 pushed:>2026-01-01"
  ],
  "maxItems": 50,
  "minLeadScore": 40,
  "includeForks": false,
  "enrichOrganizations": true,
  "maxOrganizationLookups": 20,
  "languages": ["TypeScript", "Python"],
  "githubToken": ""
}

Output fields

Field	Description
leadScore	0 to 100 lead quality score.
leadReason	Human-readable reasons behind the score.
contactabilityScore	0 to 100 score for how reachable the owner is, built only from public profile data already returned by the API.
contactabilityReason	Which public signals produced the contactability score.
contactChannels	Comma-separated list of public channels found, for example email, company website, twitter.
contactRoute	Best available route: email, website, social, or none.
outreachReady	true when at least one public contact route exists.
fullName	Repository full name.
owner / ownerType	Repository owner and whether it is a user or organization.
language	Primary repository language.
stars, forks, openIssues	GitHub traction/activity metrics.
topics	Repository topics.
website	Homepage when present.
companyDomain	Normalized company domain from the organization or repository website.
organizationName, organizationCompany	Public organization identity fields.
organizationWebsite, organizationLocation, organizationEmail	Public organization profile details when enrichment is enabled.
organizationTwitter, organizationFollowers, organizationCreatedAt	Additional public organization signals.
url	GitHub repository URL.
pushedAt, createdAt	Activity timestamps.
query	Search query that found the repo.

Example output

{
  "leadScore": 88,
  "leadReason": "high developer traction; active ecosystem/forks; recently active; organization-owned; has website; ai/devtools signal",
  "contactabilityScore": 85,
  "contactabilityReason": "public company email; company website; company social profile; company location; named company",
  "contactChannels": "email, company website, twitter",
  "contactRoute": "email",
  "outreachReady": true,
  "fullName": "example/llm-platform",
  "ownerType": "Organization",
  "language": "TypeScript",
  "stars": 2400,
  "forks": 320,
  "openIssues": 44,
  "topics": "llm, agents, devtools",
  "website": "https://example.com",
  "url": "https://github.com/example/llm-platform"
}

Contactability score

leadScore answers "is this a real, active project worth selling to". contactabilityScore answers the next question: "can I actually reach the company". It is computed only from fields the GitHub API already returns, so it never adds requests to a run.

Signal	Points
Public company email on the organization profile	40
Company website in the organization profile	20
Product website in the repository homepage, on a different domain than the company site	15
Repository homepage that points at the company's own domain	5
Public company Twitter/social handle	10
Company location	5
Named company	5
Organization with 100 or more public followers	5

contactRoute collapses the same evidence into the best single route: email first, then website, then social, and none when nothing public is available. outreachReady is true for every route except none.

Two behaviours worth knowing:

• leadScore and the minLeadScore filter are unchanged. A repository that scores 90 for traction can still score 15 for contactability when its owner publishes no email, website, or social handle; that gap is the point of the field, not a bug.
• Contactability is only as good as organization enrichment. With enrichOrganizations: false, or when GitHub rate-limits the profile lookups, owner profiles are missing and the score falls back to repository-level signals. Repository rows are still emitted, so a rate-limited run degrades rather than fails.

Query examples

topic:llm stars:>50 pushed:>2026-01-01
topic:devtools stars:>100 language:typescript pushed:>2026-01-01
topic:security stars:>50 pushed:>2026-01-01
topic:kubernetes stars:>100 pushed:>2026-01-01
topic:observability stars:>50 pushed:>2026-01-01

Pricing strategy

Pay per qualified lead:

• $0.01 actor-start fee per run,
• $0.025 qualified-lead event only when a scored repository lead is written to the dataset.

Data source and limits

• Source: public GitHub REST API.
• Unauthenticated GitHub API calls have lower rate limits. Add a GitHub token if you need higher volume.
• This Actor does not scrape private repositories or bypass access controls.

Roadmap

• Contact-page and social-profile discovery from company domains.
• Hiring signal detection from README and GitHub topics.
• Stateful monitoring for newly active repositories.