GitHub Lead Signals + AI (Companies & Developers by Tech Stack)
Pricing
from $10.00 / 1,000 ai lead scoring & outreaches
GitHub Lead Signals + AI (Companies & Developers by Tech Stack)
Find companies and developers using any technology on GitHub, enrich their public profiles, and turn them into AI-scored B2B sales leads with a buying-signal summary and a personalized outreach opener. Built-in AI, no API key.
Pricing
from $10.00 / 1,000 ai lead scoring & outreaches
Rating
0.0
(0)
Developer
Lizzy
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
GitHub Lead Signals + AI — Companies & Developers by Tech Stack
Find the companies and developers who already use a technology on GitHub and turn them into AI-scored B2B sales leads. Give it a technology or search term (e.g. stripe connect, langchain, kubernetes operator) and get back the GitHub accounts using it — enriched with their public profile plus an AI read of why they're a fit, a buying-intent signal, a sales angle, and a personalized outreach opener.
Built-in AI. No OpenAI / OpenRouter API key required. No GitHub token required.
Why "who uses this tech" is a buying signal
What an account builds with tells you what it's in the market for:
- A company with Stripe Connect repos → building marketplaces/payments → needs payments tooling, fraud, reconciliation, monitoring.
- A developer shipping LangChain / LLM repos → an AI builder → needs vector DBs, eval tools, GPU/inference.
- An org with Kubernetes operators → running cloud-native infra → needs observability, security, cost tooling.
Most GitHub scrapers just dump repos. This actor reads GitHub's public REST API (no anti-bot pain), dedupes to the account behind the repos (your actual lead), enriches their profile, and adds the layer that matters: what it means for you.
| Raw GitHub scrapers | GitHub Lead Signals (AI) | |
|---|---|---|
| Repositories matching a tech | ✅ | ✅ |
| Deduped to the company/developer (the lead) | ❌ | ✅ |
| Public profile: company, email, site, location | ❌ | ✅ |
| AI fit score (0–100) | ❌ | ✅ |
| Buying-intent signal + sales angle | ❌ | ✅ |
| Personalized outreach opener | ❌ | ✅ |
| Works with no API key | — | ✅ |
Input
| Field | Type | Description |
|---|---|---|
searchQueries | array (required) | Technologies or GitHub search strings (e.g. stripe connect, langchain, topic:fintech language:go, react stars:>500). Each is searched against repositories; the owners become your leads. |
language | string | Keep only repos in this language (e.g. TypeScript, Go). Empty = any. |
minStars | integer | Keep only repos with at least this many stars. Higher = more established. 0 = no filter. |
ownerType | select | any, organizations (companies only), or users (individual developers only). |
maxLeads | integer (1–1000) | How many unique leads to return in total. Default 50. |
enrichProfiles | boolean | Fetch each lead's public profile (company, email, website, location, Twitter, followers, bio). Default true. |
aiSignals | boolean | Built-in AI fit score, intent signal, sales angle and personalized opener. Default true. |
offerDescription | string | What you sell — the AI ties each lead's tech usage to your offer and writes a personalized opener. |
aiLanguage | string | Language for AI text. Default English. |
proxyConfiguration | object | Apify Proxy rotates IPs to stay under GitHub's rate limits. Keep the default. |
Example input
{"searchQueries": ["stripe connect", "langchain"],"minStars": 50,"ownerType": "any","maxLeads": 50,"enrichProfiles": true,"aiSignals": true,"offerDescription": "We sell a developer-focused API monitoring and observability platform.","aiLanguage": "English"}
Output
One row per unique lead (company or developer):
{"login": "stripe","ownerType": "Organization","profileUrl": "https://github.com/stripe","company": null,"email": "support+github@stripe.com","location": "San Francisco, CA","followers": 3247,"matchedRepoCount": 3,"totalStars": 869,"languages": ["Swift", "TypeScript", "JavaScript"],"topRepos": [{ "fullName": "stripe/stripe-node", "stars": 400, "language": "TypeScript" }],"leadType": "Company","techStack": ["TypeScript", "Node.js", "Stripe", "Stripe Connect"],"fitScore": 85,"intentSignal": "Repos focus on Stripe-powered payment platforms — strong need for reliable API monitoring.","salesAngle": "Emphasize reliability of their Stripe integrations in high-transaction environments.","personalizedOpener": "I noticed your work with Stripe Connect — ensuring those transactions run smoothly is exactly what we help with.","bestContactChannel": "email","aiAnalyzed": true}
How it works
- Searches GitHub's public REST API for repositories matching each query (with your
language/minStarsfilters). - Dedupes by owner — many repos can belong to one account; your lead is the account, with its top matching repos aggregated.
- Optionally enriches each lead's public profile (company, email, website, location, Twitter, followers, bio).
- Runs one AI call per lead to score fit (0–100), summarize the buying-intent signal, suggest a sales angle, and write a personalized opener tied to their real repos.
- Saves one clean lead row per account.
IPs are rotated automatically via Apify Proxy to stay under GitHub's unauthenticated rate limits, so larger runs keep flowing.
Tips
- Add an
offerDescriptionto get openers and a fit score tailored to your product. - Use
ownerType: "organizations"for B2B company lists, or"users"to recruit / reach individual builders. - Combine tech terms in
searchQueries(e.g.langchain,llamaindex,vector database) to widen an ICP in one run. - Raise
minStarsto focus on established, better-resourced accounts.
FAQ
Do I need a GitHub or AI API key? No. It uses GitHub's public REST API and Apify's built-in AI model — nothing to manage.
Is email always present?
Only when the account has published a public email on GitHub. Many do; many don't. You also get website, Twitter and location to reach the rest.
Will I get blocked? No. It reads the public JSON API and rotates IPs via Apify Proxy to respect GitHub's rate limits.
Why dedupe to the owner instead of one row per repo? Because your lead is the company or developer, not each repo. One clean row per account keeps your outreach list tidy — with the top matching repos and aggregate signal attached.
Can I turn AI or enrichment off?
Yes. Turn off aiSignals for raw leads, or enrichProfiles for just the GitHub accounts — both lower cost.
Related Actors — build a full pipeline
This Actor is the "find who uses the tech" step. Pair it with the others to go from signal → enriched contact → outreach:
- GitHub Lead Signals (this Actor) finds accounts using your target tech → feed companies into AI Lead Enricher to pull site profile, emails and a cold-email opener.
- Combine with Hiring Signals (AI) to cross-reference who's both using your tech and hiring for it — the strongest possible buying signal.
Workflow: GitHub Lead Signals (tech intent) → AI Lead Enricher (contact + opener) → your CRM / sequencer.