github-oss-maintainer-leadslisted

# Open Source and Repository Lead Generation Public repositories expose more about an engineering organisation than any other source: the languages they use, the dependencies they've adopted, how many engineers commit, how active the project is, and often the engineers' names and email addresses in the commit history. For developer tools, this is the highest-signal source available. It's also the audience most hostile to bad outreach, so the bar is high. ## Who actually buys | Context | Who decides | |---|---| | Solo maintainer's personal project | The maintainer. Usually no budget | | Company-backed OSS project | Engineering lead or founder | | Company using a library internally | Engineering manager, staff engineer, or platform lead | | Startup with public repos | Founder or CTO | | Enterprise with an OSS programme | Platform team lead, sometimes a procurement path | **Distinguish the maintainer from the buyer.** A maintainer of a popular library may have no budget at all. The companies *depending* on that library are the buyers, and dependency graphs make them findable. **Never confuse a personal project with a company.** Emailing a hobbyist's weekend repo as though it's a business is the fastest way to get publicly mocked in this community. ## Where these leads live | Source | What it gives you | Quality | |---|---|---| | Repository search by language and topic | Projects, activity, stars | Very high | | Dependency and dependents graphs | Companies using a specifi