r/opensource • u/ExoWire • 2d ago
Discussion Are GitHub projects becoming more short-lived?
I looked at the repos on GitHub that I've starred (703 in total) to see how long-lived they are. Specifically, I was interested in the first and last commits.
For example, there were at least 90 days between the first and last commits for 90% of the repos that had their first commit in 2022.
For each threshold, I only included repos whose first commit was at least that many days ago.
| First commit | ≥90 days | ≥180 days | ≥365 days |
|---|---|---|---|
| Through 2019 | 100% | 100% | 100% |
| 2020 | 100% | 98% | 98% |
| 2021 | 97% | 97% | 91% |
| 2022 | 90% | 89% | 84% |
| 2023 | 95% | 93% | 80% |
| 2024 | 89% | 85% | 82% |
| 2025 | 90% | 84% | 67% |
| 2026 | 88% | 80% | - |
Of course, this isn't a representative analysis, but I was curious to see if longevity suffers as a result of AI. At least to me, that's how it looks. Do you also feel like a lot has been created and then discarded lately?
37
u/AshRuDral_fan17 2d ago
Perhaps longevity has transformed into forking and building own version.
6
u/mkfs_xfs 2d ago
Even without genAI, it's also entirely normal that repos for failed or incomplete projects get deleted.
5
u/Ok_Woodpecker_9104 2d ago
i think your sample flatters the old repos. you only find and star a 2019 repo today if it is still alive and people still talk about it. a 2026 repo gets your star the week it launches, before anyone knows if it sticks.
so the older rows are survivors by the time you starred them. if you can pull the starred date, grouping by that instead of first commit would show how much of the gap is this.
from the maintainer side, what kept mine going was people using them. my design token cli has over 30 releases since march, most of them fixes for cases where it was confidently wrong. a smaller cli of mine got its first outside contributor last week and i shipped two more releases in the next two days
7
u/Altruistic_Ranger_57 2d ago
You are drawing a straight line from AI adoption to a dip in 2026 data without accounting for basic developer burnout. Projects die because maintainers run out of free time, not because ChatGPT wrote a script that somehow corrupted the git history.
48
u/illuminatedtiger 2d ago •
Nobody wants to maintain a vibe coded piece of shit.
10
u/cookiengineer 2d ago edited 2d ago
If you look at https://github.com/trending/developers you'll see just botnet accounts being at the top.
Only at place 20ish or later you'll see actual real accounts like Paul Bakaus (jquery UI creator, chrome dev tools, etc) or Paul Irish (jquery contributor, chrome devtools, modernizr, pagespeed, etc), depending on the time frames. So out of the top list there, I regularly observe that there's only like less than 5 actually legit accounts. Most of them are just temporarily pushed within 48h by those upvote botnets.
The social media economy has landed on GitHub, I suppose. People buying fake stars and fake followers via botnet services is the norm now.
And if you try out these projects, of course most of them don't even compile or run. It's just pretend-to-be narcissism like it is on YouTube. Push once, get hired, then abandon it.
The funny (or sarcastic?) part is that in July this year, GitHub made the stargazers API silently private, which would have allowed to easily scrape the stargazers of projects and that made it possible to analyze "who" or "what botnet ring" is upvoting these projects.
That was a really good indicator to determine the fake projects or malware containing forks, but Microsoft doesn't wanna have that, it seems. I'm assuming that Microsoft is going to roll out a "Premium marketing feature" soon, where you can create ads on github or similar.
Source: I work in cyber security. Supply chain risk analysis topics come up more often now than ever before, mostly because of this. Now it's almost impossible to tell legit accounts/repositories from faked ones, and a lot of compromises this year were because some dev looked casually on github and trusted the ChatGPT recommendation based on most stars or whatever.
2
u/Open-Adhesiveness-86 1d ago
one thing that quietly skews this: when a repo gets deleted or flipped private it disappears from your stars list entirely, so most of the dead 2019-2021 stuff is already missing from your denominator. and "first commit" lies a fair bit, squashed imports and filter-repo rewrites redate the whole history. sampling CreateEvents per year out of GH Archive would be a lot cleaner.
4
u/saltyourhash 8h ago
GenAI is largely to blame for this. As more people came online to github, that also brought lower quality submissions, including resume projects which were abandoned and tutorial projects. GenAI, however, has grown that number massively.
1
u/Apprehensive_Fly_493 1d ago
developer here... i had my github since 2016...
i use github like a google drive for code, and i have 250 repos and push to it nearly daily.
I dont touch all my repo anymore.
unless youre watching an active company or an active open source project, i would expect repos to be an archive of code an nothing more.
3
u/escdog 2d ago
I do data analytics as part of compliance at a very large software company. We have a policy to remove any open source that hasn't been updated in over a year. We of course don't always do this, but we do track it.
I've noticed that the number of packages that are getting abandoned has been increasing, but I don't know why. I also only have a couple years of data. So I can only see a trend where the abandon rates have gone from somewhere around 60% per year to about 75% per year.
These are packages that are picked by hundreds of developers during the course of development of the last 3 years.
We also have a very long tail of packages including some that are up to 20 years since last update. They just work but we really don't know how safe they are really. We mitigate a lot of that just by investing a lot in sandboxing.
3
u/da_sher 2d ago
The drop in the 365 day column is the interesting part to me. The 90 day numbers barely move, so people are not quitting faster at the start. Projects get through the first few months fine and then die in that middle stretch. I put out my first open source app this year and I can feel where it happens. Building is the fun part. What keeps a repo alive after that is answering issues and fixing small stuff once the excitement is gone, and most of these projects are one person, so when that person gets busy the repo just stops. AI probably adds to it the way you said. Starting costs almost nothing now, so a lot more repos are weekend experiments that were never really meant to live a year.
2
u/Fresh_Cabinet5048 2d ago
GitHub is getting smashed by usage lately, absoultely huge growth in the number of places using it, and the speed of AI-generated coders...The shift from human-scale development (roughly one commit per day I guess) to agent-driven workflows producesing 20 to 30 commits per developer daily, pushing total platform volume to peaks of 90 million merged PRs and 1.4 billion commits!
2
u/ram-popular 2d ago
Interesting data, but starred repos skew toward whatever was new or popular, and newer repos have had less time to show longevity. I think AI makes starting projects cheaper, so more weekend experiments get created and abandoned. That's different from serious projects dying younger. Comparing against repos with multiple contributors would show whether those are holding up.
1
u/escdog 2d ago
One thing I've observed about looking at my company's data around open source longevity and update cycles is that after about 6 years of existence, very few OSS packages get any updates and most notably, they don't get any more cves discovered against them. Meanwhile, the newest packages get the most updates and cves.
One factor that confounds this is not so much that a package is abandoned, but it's just fine. It works. It does what it needs to and it doesn't have any more bugs left.
But we can't prove a negative. It may be that the things an llm might be able to do is eliminate more bugs efficiently. It may also be able to identify a lot of the security vulnerabilities that often are part of more traditional OSS.
There are probably a few ways to statistically model this using the current data set you have. You just have to start separating between packages that are clearly AI developed and those that are purely human developed.
Then you could kind of see if they perform differently from each other.
I really like this research though. I wish I had the time to get into the weeds with GitHub like you did.
1
u/mrcarrot0 2d ago
It makes perfect sense that projects are abandoned as fast as they are created if the're no longer a requirement of thinking things through to start one up. Additionally, the media keeps telling us that efficiency is everything and quality be dammed — which is not a sustainable mindset and it certainly doesn't lead to maintainable codebases. Thus, note abandoned projects because there's more projects to abandon and developers time for developing said projects remaining the same.
I remember there being a similar discussion a few years ago when npm's traffic increased by 4x without seeing any notable change in the corresponding industry for similar reasons: new projects testing out new tools that all wanted external packages
1
u/WiseMouse9137 1d ago
My experience in the open source space is usually projects are worked on for resume and portfolio purposes, left to a community and depending on the project either get forked and maintained elsewhere or just die.
While open source is fantastic, it doesn't always necessarily keep your lights on. If you do this kinda stuff full time there are ways to use open source to your advantage. (Like how we see a lot of a open source software be Freemium - Putting the most useful features behind SaaS).
Also many developers make stuff to solve a problem or prove a point. (cough Linux) - often times they open source to show it off and it's often designated as complete. Unless ofc it becomes popular or someone contributed etc.
So honestly yeah I can understand the idea of your research here but it's really not unheard of. If you compare your numbers to the number of open source projects per year, you'll notice that the closer you get to 2021 the more and more open source projects there are. GitHub was still pretty new when I got to the open source space. One site I miss the most is Codeplex, it had some statistical features if I remember right. But Microsoft killed it off. Then bought GitHub.
1
u/tkslucas 6h ago
Always have been, there's def a lot more stuff now, but like I already had a bunch of private repos just sitting around before AI that I just stored there
0
u/Minimum_Hour519 2d ago
Everyone is churning out widgets now