# GitHub Maintainer Lead Finder (`hereditary_model/github-maintainer-leads`) Actor

Finds active repos matching your criteria and turns their top contributors into outreach-ready leads, for dev-tool sales and technical recruiting.

- **URL**: https://apify.com/hereditary\_model/github-maintainer-leads.md
- **Developed by:** [Aaron Marxsen](https://apify.com/hereditary_model) (community)
- **Categories:** Lead generation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $30.00 / 1,000 maintainer lead returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## GitHub Maintainer Lead Finder

Finding people who actually maintain the open-source tools your buyer already uses beats a cold list from a generic B2B database — they're active, technical, and self-selected into exactly the space you're selling or hiring into. This searches GitHub for repos matching your criteria and turns their top contributors into a scored, outreach-ready lead list.

### What it does

1. Searches GitHub for repos matching your language, topics, minimum stars, and recent-activity window.
2. Pulls each matching repo's top contributors by commit count.
3. Looks up each contributor's public GitHub profile — name, company, email (when they've chosen to make one public), blog, location, followers.
4. Scores each lead 0–100 on reachability: public email, listed company, personal site, follower count, and how much they've actually contributed.
5. Flags `core_maintainer` (50+ commits to this repo) and `high_influence` (500+ followers) so you can prioritize.
6. Drops anything failing your filters **before** billing.

### A note on email coverage

GitHub hides profile emails by default — most contributors, even prolific ones, won't have one public. That's real signal, not a bug: `no_public_email` shows up in `opportunitySignals` so you can see at a glance who you'll need to reach through their listed company or blog instead. Turn on `requireEmail` if you only want the subset with one.

### Input

You need your own free GitHub personal access token — GitHub allows only 60 unauthenticated requests per hour, which isn't enough for a real run. Create one with no scopes at github.com/settings/tokens; public data doesn't need any permissions.

```json
{
  "githubToken": "ghp_...",
  "language": "python",
  "topics": ["cli"],
  "minStars": 500,
  "pushedSinceDays": 90,
  "maxRepos": 20,
  "maxContributorsPerRepo": 3
}
```

### Pricing

Pay per event. You're billed per lead returned and once per repo digested, not for the GitHub API calls themselves.

# Actor input Schema

## `githubToken` (type: `string`):

Required. GitHub's API allows only 60 requests/hour without one. Create a free token with no scopes at github.com/settings/tokens (classic, no permissions needed for public data). Used only in this run's requests, never stored or shared.

## `language` (type: `string`):

Restrict to repos primarily written in this language, for example python or typescript. Leave blank for any language.

## `topics` (type: `array`):

GitHub topic tags to match, one per line, for example cli or machine-learning. Leave empty to skip topic filtering.

## `minStars` (type: `integer`):

Only repos with at least this many stars.

## `pushedSinceDays` (type: `integer`):

Only repos with a commit in the last N days, so you're reaching people who are actually still active on the project.

## `maxRepos` (type: `integer`):

Caps how many matching repos are processed, sorted by stars, highest first.

## `maxContributorsPerRepo` (type: `integer`):

How many of each repo's top contributors (by commit count) to turn into leads.

## `requireEmail` (type: `boolean`):

Drop any contributor without a public email on their GitHub profile, before billing.

## `minQualityScore` (type: `integer`):

0 to 100. Rows below this are dropped and never billed.

## Actor input object example

```json
{
  "language": "",
  "topics": [],
  "minStars": 200,
  "pushedSinceDays": 90,
  "maxRepos": 20,
  "maxContributorsPerRepo": 3,
  "requireEmail": false,
  "minQualityScore": 0
}
```

# Actor output Schema

## `leads` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("hereditary_model/github-maintainer-leads").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("hereditary_model/github-maintainer-leads").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call hereditary_model/github-maintainer-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hereditary_model/github-maintainer-leads"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/fqoea7vy1B4c5GANm/builds/ErdTLoaTnlHQsH6PJ/openapi.json