AI
What the CNCF Actually Is (in Numbers)
The Cloud Native Computing Foundation hosts 209 projects and nearly 300,000 contributors across 765 member companies. If your company is a member, you may already have access to free training and CKA certification credits. The broader cloud native community counts 135,000-plus members. This week at KubeCon, about 13,000 of them are in the same building. The Linux Foundation, which houses the CNCF, spans 900 open source projects and 51 million lines of code.
Three Maturity Levels and What They Mean for Your Stack
Projects enter the CNCF as sandbox, move to incubating, and eventually reach graduated. Sandbox projects are early-stage ideas still recruiting contributors. Incubating projects show adoption momentum but have not yet met graduation requirements. To graduate, a project must show committers from at least two organizations, documented governance, neutrality, and Linux Foundation core infrastructure best practices compliance. Both graduated and incubating projects are considered production-ready. Most projects in the landscape sit in sandbox, making them good targets for new contributors.
Reading the Landscape Without Getting Lost
The landscape at landscape.cncf.io lists all 209 projects as clickable logos. Click any one, say Helm, and you get contributor counts, maturity level, and project start date. A built-in filter tool (added recently) lets you narrow by maturity level. Filtering to graduated shows only the projects most teams already run in production. Crossplane is one that graduated recently. Each project page links directly to CLO Monitor for a deeper health check.
CLO Monitor: A Health Score for Every Project
CLO Monitor assigns a health score to every CNCF project. Green checks mean a requirement is met. Red marks show gaps, and those gaps are contribution opportunities. Helm’s CLO Monitor page shows a red X next to contributing documentation, which is an open door for anyone wanting to join a widely-used project. A score below 100 is not a disqualifier. It tells you where the project needs work and where your pull request would have real impact.
The projects.csv Download for Security-Conscious Teams
The landscape includes a download button that exports a projects.csv spreadsheet. The file includes each project’s last security audit date. If your team requires tools that have passed a security audit within a specific window, this spreadsheet lets you filter to a date range and produce a defensible list fast. The same data helps you justify tool choices to management: you can point to audit history, contributor diversity, and governance documentation from a single file.
Finding Your Place as a Contributor
Most people in the room identified as end users, not contributors. The landscape filter changes that calculus. Filter by topic area, whether security, observability, or something else, find the gap in your stack, and locate the matching sandbox or incubating project. CLO Monitor shows you exactly where a project needs help. The GitHub repo and maintainer contacts are one click away. Donating developer hours to a project your team depends on moves it closer to the features you need.
Notable Quotes
there are 209 projects at the CNCF, which is huge. Lori · ▶ 03:33
it is a marathon, not a sprint. Katherine · ▶ 07:34
just because you see red X’s does not mean it’s a deal breaker, right? It’s an opportunity. Katherine · ▶ 10:10
Find the gap in your stack and and and uh find your solution in the landscape. Lori · ▶ 14:16
Key Takeaways
- CLO Monitor health scores reveal contribution gaps in every CNCF project.
- The projects.csv download includes last security audit dates for all 209 projects.
- Sandbox projects are the fastest entry point for new contributors to make an impact.