[License Exception Request] [SOPS] [MPL-2.0 + CC BY 4.0]
Maintainers usually reply within 1 day
@krook is already working on this.
Since Aug 22, 2025.
Assessment
This issue has not been assessed yet.
Description
For which CNCF project are you requesting exceptions?
SOPS
Are you an official maintainer of this project?
Yes
List of components requiring an exception
| Component | Upstream URL | License(s) | Purpose |
|---|---|---|---|
| sops | https://github.com/getsops/sops | MPL-2.0 | Primary codebase for the SOPS project |
| docs | https://github.com/getsops/docs | CC BY 4.0 | Project Documentation |
Are all of the components mandatory dependencies for the project to function as intended?
Yes
If no, please explain
No response
How will the components be included in or with the project's code and distributions?
- Incorporated code
- Vendored component
- Build-time dependency
- Build and test tooling
- Install-time dependency
- Required upstream dependencies
- Other (please describe below)
If any of the above selections don't apply to all of the components listed in the table above, please explain
No response
Which of the following best describes how the components interact with the project's own code?
- Static linking: e.g., compiled together with project code into a single binary
- Dynamic linking: e.g., compiled into a separate binary, running together with project code in a single address space at run-time
- Separate process: e.g., separate executable running in a different process space, interacting with project code only via mechanisms such as pipes, sockets, etc.
- Network interaction only: e.g., logically separated over a network and communicating only via mechanisms such as network API call, exchanging JSON data, etc.
- Other (please describe below)
If any of the above selections don't apply to all of the components listed in the table above, please explain
Aside from the primary project codebase, the contents of the docs repository contain the project documentation
Will any of the components be modified?
No
If yes, please specify which components will be modified, and briefly describe the purpose and nature of the modifications.
No response
Will the project be seeking to contribute the modifications back to the upstream project?
No
- Dominant language
- Rich Text Format
- Stars
- 696
- Forks
- 870
- Avg merge
- 11h 5m
- Merged PRs (30d)
- 31
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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/foundation
-
code-of-conduct.md: version number is not bumped up since v1.3 (2023-06-09)May be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cncf/foundation#1109 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-3 hours Newbie friendliness 15/100
cncf/foundation#1572 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 8/100
cncf/foundation#1571 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 12/100
cncf/foundation#1570 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
cncf/foundation#1542 ·
Maintainers usually reply within 1 day