The 2026 pricing changes got me curious how the projects I actually use run their CI. So I scanned 35 well-known open-source repos (vite, next.js, prisma, astro, eslint, the usual suspects) and pulled their public GitHub Actions data: recent runs, config patterns, failure rates.
A few things genuinely surprised me.
Some workflows have been failing nearly every run. And nobody turned them off.
The one I didn't expect: trpc has a scheduled workflow ("Lock Issues & PRs") that's failing nearly every run, and it's still on. Its own scorecard flags it outright: "failing almost every run." (see it: https://gitspider.com/scan/trpc/trpc)
It wasn't alone. drizzle-orm and cal.com each have a workflow stuck in the same red-forever state.
