I share some of your sentiment on the dep mapping. We actually approach support in a variety of ways, but the dependency graph is the more novel aspect of what

I share some of your sentiment on the dep mapping. We actually approach support in a variety of ways, but the dependency graph is the more novel aspect of what we do. I _personally_ think its not overly compelling, but part of that is because of how hard it becomes to distribute any substantial amount of funds when you're trying to do it across thousands of dependencies. Outside of the dependency funding we will often directly fund developers (e.g. as contractors, which we did with rrweb back when the author was full time on the project), we subsidize a our services for open source projects (https://sentry.io/for/open-source/ https://sentry.io/for/open-source/), and we also do direct contributions in a variety of ways to organizations (some of that was listed in the post, but even things like continuous support of many community run events). People will often think a lot of these things as marketing (such as events), and they are, but its marketing that helps both sides. If we were truly lead gen oriented on these things though I can tell you it absolutely does not have the payback you'd get from some other traditional investments. Edit: One thing I did want to mention- we're not actually looking for a return on investment for these github sponsorships. We don't consider it maintenance fees, but rather as a signal of gratitude. If someone stops maintaining a project thats fine, code doesn't have to live forever. We bundle this into our annual budget at this point more from a charitable giving angle than some kind of R&D cost center.