Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[HEALTH]: SOPS

Open
  • Is something wrong?
#2,098 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Domain
security

Research direction

Start with the linked CNCF sandbox issue 157 and the SOPS entry in LFX Insights, then review the project's licensing and onboarding concerns. Gather community feedback about hard dependencies and document the TOC's decision; if archival is approved, follow the linked archival checklist across artwork, landscape, maintainer records, mailing lists, and infrastructure.

Written by the indexing model from the issue text.

Description

kind/review needs-triage review/health toc
Project name

sops

Project Health Notification Link (issue, message to mailing list etc)

https://github.com/cncf/sandbox/issues/157

Concern

The SOPS project is active but has some health issues: https://insights.linuxfoundation.org/project/sops

There's also been an issue with licensing and onboarding: https://github.com/cncf/sandbox/issues/157

The TOC should evaluate to see if the SOPS project can relicense away from MPL, if not, the project can potentially be archived or moved to a new home outside of CNCF (e..g, Linux Foundation, OpenSSF etc)

It would also be nice to hear from the community on any hard dependencies on SOPS etc before any decisions are made by the TOC.

Prior engagement

No response

Additional Information

No response

Archiving Checklist (If project is determined for archival)

NOTE: Only applicable if the project opts to self-archive, or is initiated as a last possible option following a TOC vote.
To proceed with the archival checklist, add the level/archive label and assign: caniszczyk, mrbobbytables, idvoretskyi, jeefy, castrojo, krook

Archiving Checklist
  • TOC vote to archive passed
PRs
Mailing lists
  • Remove from staff list of maintainer emails list
  • Archive (lock) maintainers mailing list (groups.io)
  • Remove mailing list from maintainers@ mailing group
  • Remove from cncf-maturity-level [email protected] (google groups)
Send emails
  • Remove project (logo) from all slide decks (contact [email protected])
  • Remove project (logo) from event sites (contact [email protected])
  • Remove from CNCF store (reach out to staff or email [email protected])
  • Archive project in LFX Insights (move to archive in PCC - Email Formation team)
Other:
  • Remove from maintainers & project from service desk
  • Check with LF IT for any CI/CD or other infrastructure the needs to be removed
Dominant language
HTML
Stars
1.9k
Forks
728
Avg merge
3d 23h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cncf/toc

All issues in cncf/toc

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.