How Open Source Projects Handle Abandoned Repositories

What this episode covers

When a maintainer walks away with no warning, what happens to the code? Lucas and Luna explore the growing problem of abandoned open source repositories — repos that are still downloaded, still depended on, but no longer maintained. They look at GitHub's dormant repo policy, the role of community forks like the Node.js io.js split, and the emerging 'maintainer last will' movement where developers leave handover instructions. Concrete numbers: roughly 1 in 5 npm packages have had no update in over a year, and the average time to first response on an abandoned repo issue is 647 days. They discuss real cases like the left-pad incident, Ruby on Rails' governance docs for succession, and why the 'bus factor' is finally getting the attention it deserves. If you depend on open source — and who doesn't — this episode shows why abandonment is infrastructure risk, not just a developer inconvenience. #OpenSource #AbandonedRepos #MaintainerBurnout #BusFactor #LeftPad #NodeJS #iojs #NPM #RubyOnRails #GitHub #SoftwareMaintenance #InfrastructureRisk #CommunityFork #DependencyHell #TechDebt #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

PodParley-generated summary based on available episode metadata and transcript content.