|
| 1 | +# .project metadata for Cedar |
| 2 | +# Documentation: https://github.com/cncf/automation/tree/main/utilities/dot-project |
| 3 | + |
| 4 | +# TODO: Add maintainer GitHub handles |
| 5 | +# TODO: Add maturity_log entry with TOC issue URL |
| 6 | +# TODO: Set project_lead GitHub handle |
| 7 | +# TODO: Set cncf_slack_channel |
| 8 | +# TODO: Set identity_type under legal (has_dco, has_cla) |
| 9 | +# TODO: Add adopters list (ADOPTERS.md) |
| 10 | +# TODO: Add package_managers if distributed via registries |
| 11 | + |
| 12 | +schema_version: "1.0.0" |
| 13 | +slug: "cedar" |
| 14 | +name: "Cedar" |
| 15 | +description: "Cedar is an open source authorization policy language that enables developers to express fine-grained permissions as easy-to-understand policies enforced in their applications, and decouple access control from application logic. Cedar is designed to be ergonomic, fast, safe, and analyzable using automated reasoning. Cedar's simple and intuitive syntax supports common authorization use-cases with readable policies, naturally expressing concepts from role-based, attribute-based, and relation-based access control models. Cedar's policy structure enables authorization requests to be decided quickly. Its policy validator uses optional typing to help policy writers avoid mistakes, but not get in their way. Cedar's design has been finely balanced to allow for a sound, complete, and decidable logical encoding, which enables precise automated analysis of Cedar policies, e.g., to ensure that policy refactoring preserves existing permissions. Cedar's language specification has been formally verified using a theorem prover to satisfy key security properties like "deny trumps allow," and its implementation in Rust undergoes rigorous differential random testing against its formal specification. By combining mathematical rigor with developer-friendly design, Cedar offers a practical approach to secure, maintainable authorization for modern applications." |
| 16 | +type: "project" |
| 17 | +# TODO: Set project lead GitHub handle |
| 18 | +# project_lead: "github-handle" |
| 19 | +# TODO: Set CNCF Slack channel |
| 20 | +# cncf_slack_channel: "#cedar" |
| 21 | + |
| 22 | +maturity_log: |
| 23 | + - phase: "sandbox" |
| 24 | + date: "2026-03-18T14:36:03Z" |
| 25 | + issue: "https://github.com/cncf/toc/issues/XXX" # TODO: Set TOC issue URL |
| 26 | + |
| 27 | +repositories: |
| 28 | + - "https://github.com/cedar-policy/cedar" |
| 29 | + |
| 30 | +website: "https://cedarpolicy.com" |
| 31 | + |
| 32 | +artwork: "https://landscape.cncf.io/logos/cedar.svg" |
| 33 | + |
| 34 | +# TODO: Add ADOPTERS.md if your project tracks adopters |
| 35 | +# adopters: |
| 36 | +# path: "https://github.com/cedar-policy/cedar-policy/blob/main/ADOPTERS.md" |
| 37 | + |
| 38 | +# TODO: Add package manager identifiers if your project is distributed via registries |
| 39 | +# package_managers: |
| 40 | +# docker: "cedar-policy/cedar-policy" |
| 41 | + |
| 42 | + |
| 43 | +security: |
| 44 | + policy: |
| 45 | + path: "https://github.com/cedar-policy/cedar-policy/blob/main/SECURITY.md" |
| 46 | + contact: |
| 47 | + advisory_url: "https://github.com/cedar-policy/cedar-policy/security/advisories/new" |
| 48 | + |
| 49 | +governance: |
| 50 | + contributing: |
| 51 | + path: "https://github.com/cedar-policy/cedar-policy/blob/main/CONTRIBUTING.md" |
| 52 | + code_of_conduct: |
| 53 | + path: "https://github.com/cncf/foundation/blob/main/code-of-conduct.md" |
| 54 | + |
| 55 | +legal: |
| 56 | + license: |
| 57 | + path: "https://github.com/cedar-policy/cedar-policy/blob/main/LICENSE" |
| 58 | + identity_type: |
| 59 | + has_dco: true |
| 60 | + has_cla: false |
| 61 | + dco_url: |
| 62 | + path: "https://developercertificate.org/" |
| 63 | + |
| 64 | + |
| 65 | +landscape: |
| 66 | + category: "Provisioning" |
| 67 | + subcategory: "Security & Compliance" |
| 68 | + |
0 commit comments