toc
⚖️ The CNCF Technical Oversight Committee (TOC) is the technical governing body of the CNCF Foundation.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/cncf/toc with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/cncf/toc'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/cncf--toc)HTML
<a href="/listings/cncf--toc"><img src="/api/listings/cncf--toc/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 123 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # CNCF Technical Oversight Committee (TOC)
- The CNCF TOC is the technical governing body of the CNCF. It admits and oversees all projects in the CNCF and has a mandate to facilitate driving neutral consensus for:
- * defining and maintaining the technical vision and [principles](https://github.com/cncf/toc/blob/main/PRINCIPLES.md) for the Cloud Native Computing Foundation,
- * approving new projects within the scope of the CNCF set by the Governing Board (GB), creating a conceptual architecture for the projects, aligning projects, removing or archiving projects,
- * accepting feedback from end user technical advisory board and map to projects,
- * aligning interfaces to components under management (code reference implementations before standardizing), and defining common practices to be implemented across CNCF projects, if any.
- ## TOC Technical Vision
- The technical direction of the ecosystem is problem-centric. We encourage and support our projects to solve problems faced by adopters, to build the right ecosystem for innovation and embrace changes in the broader technical landscape. To exercise and increase the expertise within the technical community to compose solutions that stand the test of time.
- ## TOC Members
- * **Ahmed Bebars** (term: 2 years - start date: 5/12/2026 - 5/12/2028) [EndUser-appointed]
- * **Alex Chircop** (term: 2 years - start date: 3/4/2025 - 3/4/2027) [TOC-appointed]
- * **Brandt Keller** (term: 2 years - start date: 5/12/2026 - 5/12/2028) [TOC-appointed]
- * **Chad Beaudin** (term: 2 years - start date: 3/4/2025 - 3/4/2027) [EndUser-appointed]
- * **Faseela K** (term: 2 years - start date: 3/4/2025 - 3/4/2027) [GB-appointed]
- * **Jeremy Rickard** (term: 2 years - start date: 3/4/2025 - 3/4/2027) [GB-appointed]
- * **Joseph Sandoval** (term: 2 years - start date: 5/12/2026 - 5/12/2028) [GB-appointed]
- * **Karena Angell** (term: 2 years - start date: 3/4/2025 - 3/4/2027) [GB-appointed][TOC Chair]
- * **Kevin Wang** (term: 2 years - start date: 5/12/2026 - 5/12/2028) [GB-appointed]
- * **Mario Fahlandt** (term: 2 years - start date: 5/12/2026 - 5/12/2028) [GB-appointed]
- * **Mauricio Salatino** (term: 2 years - start date: 5/12/2026 - 5/12/2028) [Maintainer-appointed]
- ## TOC Alternates
- * **Katie Gamanji** (term: 1 year - start date: 5/12/2026 - 5/12/2027) [GB-appointed][alternate]
- * **Ricardo Aravena** (term: 1 year - start date: 5/12/2026 - 5/12/2027) [TOC-appointed][alternate]
- Note: TOC Alternates are non-voting members of the TOC
- Election [schedule](operations/election-schedule.md)
- ## TAG / TCG Liaisons
- * **Karena Angell** ([@angellk](https://github.com/angellk)) — TAG Security and Compliance
- * **Brandt Keller** ([@brandtkeller](https://github.com/brandtkeller)) — TAG Infrastructure, TCG Platform Engineering
- * **Faseela K** ([@kfaseela](https://github.com/kfaseela)) — TAG Infrastructure, TAG Operational Resilience, TCG Environmental Sustainability
- * **Alex Chircop** ([@chira001](https://github.com/chira001)) — TAG Workloads Foundation, TAG Infrastructure, TCG Platform Engineering
- * **Kevin Wang** ([@kevin-wangzefeng](https://github.com/kevin-wangzefeng)) — TCG Artificial Intelligence, TCG Environmental Sustainability
- * **Mauricio Salatino** ([@salaboy](https://github.com/salaboy)) — TAG Developer Experience, TAG Operational Resilience, TCG Artificial Intelligence
- * **Mario Fahlandt** ([@mfahlandt](https://github.com/mfahlandt)) — TAG Security and Compliance, TAG Operational Resilience, TCG Software Supply Chain Security
- * **Chad Beaudin** ([@chadbeaudin](https://github.com/chadbeaudin)) — TAG Operational Resilience, TAG Workloads Foundation
- * **Ahmed Bebars** ([@abebars](https://github.com/abebars)) — TAG Developer Experience
- * **Jeremy Rickard** ([@jeremyrickard](https://github.com/jeremyrickard)) — TAG Workloads Foundation, TAG Operational Resilience
- * **Joseph Sandoval** ([@jrsapi](https://github.com/jrsapi)) — TAG Developer Experience, TAG Workloads Foundation
- ## Projects
- See the [current CNCF projects](https://www.cncf.io/projects/) and a description of project maturity levels (Sandbox, Incubating, Graduated).
- The CNCF provides a [list of services](https://www.cncf.io/services-for-projects/) for incubating and graduated projects hosted in the foundation. A subset of these services is also available for [Sandbox](https://www.cncf.io/sandbox-projects/) level projects.
- Do you want to contribute to a project? We have a [guide](https://contribute.cncf.io/contributors/) to get you started.
- If you would like to know more about the project lifecycle we use, we have [outlined the process](https://github.com/cncf/toc/blob/main/process/README.md). If you have any questions or don't know where to start, please open an [issue](https://github.com/cncf/toc/issues).
- ## Meeting Time
- The TOC meets on the 1st and 3rd Tuesday of every month at 8AM PT (USA Pacific Time; [Convert to local time zone](http://www.thetimezoneconverter.com/?t=8:00AM&tz=San%20Francisco)).
- Here is a [calendar for all public CNCF events](https://zoom-lfx.platform.linuxfoundation.org/meetings/cncf?view=week). This calendar is also available on the [CNCF Website](https://www.cncf.io/calendar/) Meetings can be joined directly form the calendar.
- ## Meeting Agenda and Minutes
- - [Meeting Agenda and Minutes](https://github.com/cncf/toc/issues?q=is%3Aissue%20label%3Akind%2Fmeeting%20)
- - [Archive (2018.10~2024.08) of Meeting Working Doc](https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit#). This includes minutes from previous meetings.
- - [Archive (2016.02~2019.06) of Meeting agenda and presentations](resources/meeting_presentations.md).
- - [Archive (2016.04~2018.11) of community presentations](resources/scheduled_presentations.md)
- - [CNCF TOC Playlist on YouTube](https://www.youtube.com/playlist?list=PLj6h78yzYM2Mf6GCZzW6CAk6GlZESbemB)
- ## Mailing List
- Public mailing list for the CNCF TOC: cncf-toc@lists.cncf.io
- The public mailing archive: https://lists.cncf.io/g/cncf-toc
- Details to join this public mailing list: https://lists.cncf.io/mailman/listinfo/cncf-toc
- In case you need to reach the CNCF TOC on sensitive issues, please email us at: cncf-private-toc@lists.cncf.io
- ## Slack
- Public CNCF TOC channel: Join the [CNCF slack](https://slack.cncf.io/) and we are reachable at [#toc](https://cloud-native.slack.com/archives/C0MP69YF4).
- ## Voting
- This is our [voting policy](https://github.com/cncf/toc/blob/main/operations/toc-decision-process.md#voting). Only TOC members can cast binding votes. (+1 Binding)
- ## Technical Advisory Groups and TOC SubProjects
- ### Technical Advisory Groups
- * [TAG Developer Experience](./tags/tag-developer-experience/)
- * [TAG Infrastructure](./tags/tag-infrastructure/)
- * [TAG Operational Resilience](./tags/tag-operational-resilience/)
- * [TAG Security and Compliance](./tags/tag-security-and-compliance/)
- * [TAG Workloads Foundation](./tags/tag-workloads-foundation/charter.md)
- ### TOC SubProjects
- * [Contributor Strategy and Advocacy SubProject](./toc_subprojects/contributor-strategy-and-advocacy-subproject)
- * [Mentoring SubProject](./toc_subprojects/mentoring-subproject/)
- ## Technical Advisory Groups - Archived
- The TOC has approved the formation of [TAGs](./.archive/README.md).
- The following Technical Advisory Groups have been archived:
- * [TAG-Security](https://github.com/cncf/tag-security)
- * [TAG-Storage](https://github.com/cncf/tag-storage)
- * [TAG-App-Delivery](https://github.com/cncf/tag-app-delivery)
- * [TAG-Network](https://github.com/cncf/tag-network)
- * [TAG-Runtime](https://github.com/cncf/tag-runtime)
- * [TAG Contributor Strategy](https://github.com/cncf/tag-contributor-strategy)
- * [TAG Observability](https://github.com/cncf/tag-observability)
- * [TAG Environmental Sustainability](https://github.com/cncf/tag-env-sustainability)
- These Technical Advisory Groups have been spun down and replaced with new Technical Advisory Groups and TOC SubProjects, listed above.
- ### Updating TAG or SubProject README files
- To modify the README files for individual TAGs or TOC SubProjects, please **do not edit them directly**. Instead, the source of truth for these files is the [`tags.yaml`](https://github.com/cncf/toc/blob/main/tags.yaml) file. To understand the process for updating these READMEs by modifying `tags.yaml`, please refer to the [Updating TOC TAG and SubProject README Files document](./generator/updating-tag-and-toc=subproject-readme-files.md).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.