GitHub Tech Adoption Lead Finder

Find companies actually using a technology based on verifiable public GitHub evidence.

This Apify Actor helps B2B sales, partnerships, developer relations, and GTM teams identify organizations whose public GitHub repositories show real adoption of a framework, SDK, API, database, package, or developer tool.

It is not a generic GitHub repository scraper. A repository description or README mention is not enough for a high-confidence lead. The Actor looks for concrete signals such as dependency manifests, SDK imports, configuration keys, technology-specific files, and initialization code, then deduplicates results into unique company leads.

Example Use Cases

• Find companies using Supabase, Stripe, Prisma, Sentry, Clerk, Auth0, LangChain, or Pinecone.
• Build account lists from public developer adoption signals.
• Prioritize leads with recent development activity.
• Enrich GitHub organizations with public website, contact, careers, and metadata signals.
• Export clean CSV-ready company leads instead of many duplicate repository rows.

Input

{
  "technology": "Supabase",
  "packageNames": ["@supabase/supabase-js"],
  "technologyAliases": ["supabase"],
  "maxResults": 100,
  "minimumRecentActivityDays": 365,
  "companyOnly": true,
  "includeForks": false,
  "minimumConfidence": 70
}

Fields

• technology required: Technology, framework, SDK, package, API, database, or developer tool.
• packageNames: Optional exact package names to treat as strong dependency evidence.
• technologyAliases: Optional aliases and keywords used for discovery and matching.
• languages: Optional GitHub language filters.
• maxResults: Maximum number of unique company leads to output. A billable result should represent one unique company lead.
• maxRepositoriesToInspect: Safety cap for repository verification work.
• minimumStars: Optional repository star threshold. Stars are not the primary lead quality signal.
• minimumRecentActivityDays: Recent activity window. Set 0 to disable.
• includePersonalRepositories: Include user-owned repositories when they appear business-related.
• includeForks: Include forked repositories.
• companyOnly: Exclude owners that cannot be tied to a company or organization.
• minimumConfidence: Minimum deterministic technology confidence score.
• githubToken: Optional GitHub token. Prefer Apify secrets or the GITHUB_TOKEN environment variable.
• concurrency: Number of repositories to inspect concurrently.
• includeWebsiteEnrichment: Fetch a small amount of public website metadata when available.

Technology Detection

The Actor includes a mapping system for common technologies so users do not need to know every package name. Current built-in mappings include:

• Supabase: @supabase/supabase-js, Python supabase, Supabase config keys.
• Stripe: stripe, @stripe/stripe-js, Python/Ruby/PHP Stripe packages, Stripe config keys.
• Prisma: @prisma/client, prisma, prisma/schema.prisma.
• Sentry: @sentry/*, sentry-sdk, github.com/getsentry/sentry-go, Sentry config keys.
• Auth0, Clerk, LangChain, and Pinecone.

You can add technologies by extending src/detection/technologies.ts.

Evidence And Confidence

Every output lead includes actual evidence from a public repository file.

Strong evidence:

• Direct dependency in a manifest.
• SDK import statement.
• SDK initialization.

Medium evidence:

• Technology-specific configuration.
• Technology-specific files or deployment setup.

Weak evidence:

• README or documentation mention.

Weak evidence alone normally stays below the default confidence threshold. Scores are deterministic and include confidenceReasons.

Output

Each dataset item represents one unique company lead by default.

{
  "technology": "Supabase",
  "companyName": "Example Inc",
  "githubOrganization": "example",
  "githubOrganizationUrl": "https://github.com/example",
  "companyWebsite": "https://example.com",
  "location": "New York, NY",
  "publicEmail": "hello@example.com",
  "repository": "example/product",
  "repositoryUrl": "https://github.com/example/product",
  "repositoryDescription": "Production application",
  "repositoryStars": 42,
  "repositoryLastUpdated": "2026-09-01T12:00:00Z",
  "evidenceType": "package dependency",
  "evidenceFile": "package.json",
  "evidenceValue": "@supabase/supabase-js",
  "technologyConfidence": 95,
  "confidenceReasons": [
    "Direct dependency found in package.json",
    "Repository updated within last 30 days"
  ],
  "repositoriesUsingTechnology": 3,
  "leadQualityScore": 91,
  "companyVerified": true,
  "contactPage": "https://example.com/contact",
  "careersPage": "https://example.com/careers",
  "discoveredAt": "2026-09-11T08:00:00.000Z"
}

The full item also includes evidenceRepositories, a compact list of the strongest supporting repositories for that company.

GitHub API Behavior

For best results, provide a GitHub token with read access to public repositories. The Actor does not automate GitHub login and does not access private repositories.

With a token:

• Uses GitHub REST code search to discover file-level evidence.
• Applies retry and rate-limit handling.
• Inspects supporting files through the official contents API.

Without a token:

• Code search is skipped.
• The Actor falls back to repository search and common manifest/config file inspection.
• GitHub API rate limits are much lower.

Website Enrichment

When includeWebsiteEnrichment is enabled, the Actor fetches the public website listed on the GitHub owner profile and extracts only basic, explicitly public information:

• Page title and meta description.
• Contact and careers links.
• Publicly displayed email addresses.
• LinkedIn company link if present.

Website enrichment uses short timeouts and does not crawl hundreds of pages. Website errors never fail the whole run.

Filtering

The Actor avoids common false positives:

• Tutorial, demo, starter, example, coursework, documentation, and awesome-list repositories.
• Forks when includeForks is disabled.
• Template and archived repositories.
• Repositories owned by the technology vendor.
• Description-only or README-only mentions as strong evidence.

Limitations

• Public GitHub data is incomplete and may not reflect private production systems.
• GitHub code search quality and rate limits depend heavily on token availability.
• Company identification is conservative. The Actor does not guess private emails or invent company data.
• Personal repositories are excluded by default unless business ownership is apparent.
• Website enrichment only uses small public-page fetches.

Development

npm install
npm run build
npm test
npm run lint
npm start

Local Actor input is read from Apify local storage. On the Apify platform, use the input UI generated from .actor/input_schema.json.

Store Readiness Notes

This Actor is structured so pay-per-result pricing can be added later with one result equal to one unique company lead, not every repository or file inspected.

Before publishing, run live checks with a GitHub token for at least Supabase, Stripe, and Prisma, inspect the dataset manually, and verify that each result contains real file-level evidence and clean company-level deduplication.