What happened
GitHub announced that its community-driven funding program has crossed $100 million in total payments distributed to open-source maintainers — money contributed directly by developers, companies, and organizations through GitHub Sponsors and related giving mechanisms. The milestone reflects years of incremental contributions rather than a single corporate grant. Separately, Vercel released a new feature allowing teams to manually purge build and CI artifacts stored in its Remote Cache, giving engineering teams finer control over what cached data persists between pipeline runs.
Why it matters for your business
For CTOs and engineering leaders who rely on open-source dependencies — which is to say virtually all of them — the GitHub milestone is evidence that direct maintainer funding is becoming a normalized line item in the software supply chain. Companies that sponsor the libraries underpinning their products reduce the risk of unmaintained, vulnerable code slipping into production. On the Vercel side, the ability to purge Remote Cache artifacts is a practical win for teams troubleshooting stale builds or rotating secrets embedded in CI environments. Previously, stale cache artifacts could silently cause incorrect build outputs or prolong exposure to outdated dependencies; a manual purge mechanism addresses both concerns directly and reduces debugging time.
What to watch next
GitHub's $100 million figure is likely to accelerate corporate participation in open-source sponsorship as procurement and security teams increasingly tie vendor evaluations to software supply chain health. Expect more enterprises to formalize OSS funding budgets in 2025. On the tooling side, Vercel's cache controls point toward a broader industry trend of giving platform teams more granular observability and override capabilities within CI/CD pipelines — a pattern likely to appear in competing platforms in the near term.