Find Idris 2 and Type-Driven Developer Leads on GitHub

Who Are Idris 2 and Dependent Type Developers?

Developers working with Idris 2, Agda, Lean 4, Coq, and other dependently-typed languages are a concentrated and highly technical audience: PL researchers, formal verification engineers, compiler developers, proof assistant contributors, and advanced functional programmers. They engage deeply with correctness, type safety, and mathematical proofs in software.

For developer tool companies building type checkers, proof automation tools, verification platforms, language servers, or advanced IDE integrations, this audience represents a sophisticated early adopter segment. GitLeads captures their GitHub activity — new stars on language repos, keyword mentions in issues and discussions — and routes enriched profiles into your existing sales tools.

GitHub Repos and Signals to Track

• **Idris 2 signals** — `idris-lang/Idris2`, `idris-lang/idris2-pack`, `stefan-hoeck/idris2-sop`
• **Lean 4 signals** — `leanprover/lean4`, `leanprover-community/mathlib4`, `leanprover/verso`
• **Agda signals** — `agda/agda`, `agda/agda-stdlib`, `agda/cubical`
• **Coq/Rocq signals** — `coq/coq`, `coq-community/awesome-coq`, `rocq-prover/rocq`
• **Koka signals** — `koka-lang/koka` (algebraic effects, type-driven)
• **Keyword signals** — "dependent types", "type theory", "proof assistant", "formal verification", "totality checker" in issues/discussions
• **Academic signals** — "PLDI", "ICFP", "CPP conference" keyword mentions indicate PL community engagement

Sample Lead Profile: Lean 4 Developer

{
  "signal_type": "stargazer",
  "repo": "leanprover/lean4",
  "developer": {
    "github_username": "proofsmith_kai",
    "name": "Kai Lindström",
    "email": "kai@verifylabs.se",
    "company": "VerifyLabs",
    "bio": "PL researcher • Lean 4 contributor • formal verification for embedded systems",
    "location": "Gothenburg, SE",
    "followers": 320,
    "top_languages": ["Lean", "Idris", "Haskell", "Agda"],
    "public_repos": 22,
    "profile_url": "https://github.com/proofsmith_kai"
  },
  "signal_context": "starred leanprover/lean4",
  "enriched_at": "2026-05-09T11:30:00Z"
}

Setting Up GitLeads for Dependent Type Developer Signals

1. Sign up at gitleads.app and connect your GitHub account
2. Add tracked repos: `idris-lang/Idris2`, `leanprover/lean4`, `agda/agda`, `coq/coq`, `koka-lang/koka`
3. Add keyword signals: "dependent types", "type theory", "proof assistant", "formal verification", "totality checker"
4. Connect your destination: HubSpot, Salesforce, Slack, Clay, or webhook
5. Receive enriched developer profiles in real-time as signals fire

Segmentation Strategies for Dependent Type Leads

• Lean 4 + "mathlib" keyword → mathematician/researcher → formal math tooling pitch
• Idris 2 + "embedded" or "systems" keyword → safety-critical software developer → verification tool pitch
• Agda + "cubical" keyword → HoTT researcher → advanced type theory tooling pitch
• Coq + "CompCert" or "seL4" keyword → verified systems developer → industrial verification pitch
• Any repo + > 500 followers → language ecosystem influencer → developer advocate or partnership outreach
• Koka star + "effects" keyword → effect system researcher → PL tooling pitch

Routing Dependent Type Developer Leads

• HubSpot — create contact with "PL researcher" or "formal verification" persona tag
• Slack — alert #research-gtm channel for Lean 4 / Agda contributors with 200+ followers
• Clay — enrich with institutional affiliation (university vs. industry) for targeted pitch
• Salesforce — create Lead with signal source, route to technical sales rep
• Airtable/Notion — build a researcher tracker for long-cycle outreach and conference targeting