Is open source broken and does it need to be fixed?
Is open source broken, breaking, or is this just the new normal?
We are in the middle of a disruptive avalanche in software. Open source drove the last major disruption, but now open source is in the center of this one. There are more packages than we can count. More vulnerabilities than we can imagine. More malware than we want. The package registries are all bursting at the seams. Maintainers are burning out left and right. It feels dire.
There’s also not really one “open source”, it’s actually millions of little things. We like to group it all together, but that’s inaccurate. Every aspect of open source has different challenges both on the production and consumption side. We can’t solve any of these problems without understanding them first.
Who is behind maintaining all this open source software; how can we figure out which of these open source dependency vulnerabilities matter; what’s up with all this malware, and what are some simple steps we can take to avoid it; are the package registries and maintainers actually burning out, and if they are, what can we do about it; should I just use AI to rewrite all my open source.
In this talk, we will first break down the data and look at larger open source trends. We need to understand what’s happening with all the vulnerabilities, and malware, and packages, and just … everything. Then we can start to look at what’s being done today to address some of the challenges, and talk about what’s coming next. Some changes are systemic, some are quick wins, and some things we have no idea what to do.