Automated Governance: does the TAG want it back as an initiative, and where do its documents live?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation
Research direction
Read the archived working group's README and Automated Governance Maturity Model in cncf/tag-security, then inspect the successor materials under cncf/toc/tags/tag-security-and-compliance/. Confirm the TAG's decision on whether the initiative returns and where its documents should live; done means that decision is recorded, with a carry-across PR only if requested.
Written by the indexing model from the issue text.
Description
Automated Governance has a finished deliverable and no longer has a home in the tree. The working group's README and the Automated Governance Maturity Model both sit in cncf/tag-security, archived and last pushed 2025-12-08. The controls catalog and supply-chain work that succeeded it sit in cncf/toc/tags/tag-security-and-compliance/.
The maturity model is about eighteen kilobytes of finished text. It gives an organization a scale for the maturity of the controls an automated governance programme needs, without scoring a specific implementation.
Does the TAG want Automated Governance back as an initiative, and where do its documents live now the source repository is archived? If the answer to the first is yes, I will do the carry-across. That means porting the maturity model to the new location, opening the PR, and taking the initiative's maintenance.
The scale has a shipped consumer: four admission rails, OPA rego, Kyverno CEL, Kyverno JMESPath and CUE, run in CI at https://github.com/probityai/agent-evidence-admission
Edited 2026-09-22: updated a repository URL to its current path, and split one long sentence in two.
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 728
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cncf/toc
-
kind/review needs-triage review/health toc
Difficulty 5/5 Over a week Newbie friendliness 5/100
Maintainers usually reply within 1 day
-
kind/initiative needs-group needs-triage
Difficulty 5/5 Over a week Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
[Initiative]: Telco AI NativePossibly taken @kashifest claimed this 4 days ago. Openkind/initiative tag/infrastructure triage/valid
Difficulty 5/5 Over a week Newbie friendliness 20/100
cncf/toc#2314 · 13 comments · 2 reactions · 1 assignee ·
Maintainers usually reply within 1 day
-
kind/initiative needs-group needs-triage
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
[LEVEL CHANGE] Meshery Sandbox to IncubationMay be free again @riaankleinhans claimed this 28 days ago, and no pull request is open. Openkind/moving-levels toc triage/valid
cncf/toc#2302 · 1 reaction · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
RustCrypto/SSH#596 ·
-
Translation TwigBridge
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
symfony/symfony-docs#23308 ·
Maintainers usually reply within 3 days
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 4 days
-
Перевод устарел
Difficulty 1/5 Under an hour Newbie friendliness 88/100