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.
• Scores each repo from 0 to 100 using traction, recent activity, organization ownership, website presence, and B2B category signals.
• 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,
  "languages": ["TypeScript", "Python"],
  "githubToken": ""
}

Output fields

Field	Description
leadScore	0 to 100 lead quality score.
leadReason	Human-readable reasons behind the score.
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.
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",
  "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"
}

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:

• small actor-start fee per run,
• 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

• Organization profile enrichment.
• Domain/company extraction from repo homepages.
• Hiring signal detection from README and GitHub topics.
• Stateful monitoring for newly active repositories.