Contribo
ProgramsOrganizationsProjectsProposal StudioResourcesOrbit AIDashboard
Login
Login
Contribov1.0

Your premium companion for discovering, matching, and tracking paid open-source mentorship programs and verified starter issues.

Product

  • Programs Directory
  • Orbit AI
  • User Dashboard

Resources

  • Guides & Resources
  • Proposal Studio

Community

  • GitHub Repository
  • Code of Conduct

Legal

  • Privacy Policy
  • Terms & Conditions
  • Cookie Policy
  • Accessibility Statement

Made with love bySubhranshu Sekhar Dash

© 2026 Contribo. Built for the global open-source community.

PlatformProjects

Explore Projects

Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.

Confused which project to choose or don't know which one you are most suitable to work on?

Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.

Match with Orbit AI
Filters Clear
1243 Projects Found
Sort by

SIG Docs Localization: AI-era localization automation (2026 Term 1)

Intermediate
•Varies

Ready to Apply?

Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.

Start Proposal
Proposal Status
0% ProgressNot Started
Accepted Proposals
3 SimilarView →
Proposal Guide
Tailored DocsOpen →
Checklist & Review
Readiness AuditCheck →
175h (Medium)

This project focuses on improving localization workflows in Kubernetes SIG Docs by strengthening visibility, prioritization, and traceability across English and localized documentation. The enhanced workflows will benefit to reducing review burden and coordination costs that arise in environments where upstream content changes and subsequent localization efforts occur asynchronously. The project also explores practical approaches to achieving measurable productivity gains by adopting AI-assisted tools within established human workflows. Mentees work with mentors in SIG Docs localization to improve existing localization review and coordination processes, such as label-based coordination and review signals implemented through Prow/CI. The project focuses on the following core areas: improving traceability between frequently changing English content and localized documentation, continuously tracking and notifying review priorities for translation updates, and maintaining visibility into localization coverage and prioritization based on document importance. All outcomes are designed to integrate naturally into existing SIG Docs GitHub workflows and practices while preserving and supporting human-led review and decision-making. - Expected Outcome: - Reusable Prow/CI automation prototypes - Extensible architecture - Best practices documentation

TBA
Proposal

Release engineering: add Kubescape to commonly-requested package managers

Intermediate
•Varies175h (Medium)

The Kubescape client binary is built from GitHub using standard patterns. Support for homebrew and krew exists, but users have requested RPM and DEB packages. In this project you will stabilize the delivery of new builds to existing package managers, and implement support for RPM and DEB packages using GitHub Actions. Expected Outcome: When a new Kubescape version is released, it is available in homebrew, krew, RPM and DEB repositories.

TBA
Proposal

Governance Documentation (2024 Term 1)

Intermediate
•Varies175h (Medium)

This project will focus on governance documentation for the Cilium project with two key parts. First, the governenace documentation should be moved out of the main docs and into the community repo. Second, we need to do an inventory of all of the repos under the project and come up with a lifecycle for them. Expected Outcome: Governance docs in community repo. All repos accounted for and with a lifecycle plan. Recommended Skills: enthusiasm for governance and basic markdown experience Upstream Issues: - https://github.com/cilium/community/issues/78 - https://github.com/cilium/community/issues/27 - https://github.com/cilium/community/issues/82

TBA
Proposal

Implement typed function references proposal

Intermediate
•Varies175h (Medium)

Description: WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for cloud native, edge, and decentralized applications. WasmEdge is an official sandbox project hosted by the CNCF. This proposal is one of the requirements for GC proposal. Typed function references proposal adds function references that are typed and can be called directly.

TBA
Proposal

Open Mainframe Project 2020 Mentorship - Enhance zvm Prometheus exporter Mentorship Project

Intermediate
•Varies175h (Medium)

Enhance z/vm Prometheus exporter, as https://github.com/zvmexporter/zvm_exporter is pretty old and some stuffs like xcat is not maintained anymore, we propose to use Feilong as base to enhance Prometheus exporter and to provide more metrics to help ecosystem build up

TBA
Proposal

Integrating CNCF Fuzzing Framework for Envoy Gateway (2025 Term 1)

Intermediate
•Varies175h (Medium)

Envoy Gateway has become a crucial part of modern cloud-native infrastructures, providing a simplified way to deploy and manage Envoy Proxy. Ensuring the reliability and security of Envoy Gateway is paramount for its growing user base. Fuzzing, a widely-used technique for identifying software vulnerabilities and bugs, can significantly enhance the robustness of Envoy Gateway. By integrating the CNCF Fuzzing Framework, this project aims to improve the security posture of Envoy Gateway through comprehensive automated testing. Expected Outcome: Add a fuzz test that covers 80% of code paths for translating Gateway API input configuration into xDS output. Enable continuous fuzzing using OSS-Fuzz.

TBA
Proposal

Hyperledger Cello - Operate Blockchain Network in an Efficient Way Mentorship Project

Intermediate
•Varies175h (Medium)

Today, most users adopt Blockchain in order to collaborate with each other, however, it is difficult to manage a large blockchain network because of multiple organizations and nodes. Hyperledger Cello is aiming to resolve the following challenges, 1) Facilitate creation of blockchain network, can help user without blockchain background to setup their network nodes quickly. 2) Cross organization communication, can connect blockchain networks among multiple organizations. This project targets to design and implement a practical operational system equipping with decentralized functionalities to solve above challenges, based on Hyperledger Cello code base. Learning Objectives 1) Work closely with community experts and developers to learn the open-source culture and skills; 2) Learn the advanced knowledge inside the blockchain and distributed ledgers; 3) Practice hand-on experience with web application design and implement. Expected Outcome Help design and implement the blockchain operation dashboard and api server.

TBA
Proposal

Adding cSONiC support in sonic community testbed topology Mentorship Project

Intermediate
•Varies175h (Medium)

*OPEN TO US BASED STUDENTS ONLY* - Accepting applications until May 23, 2025 Currently, SONiC community testbed use vendor NOS (cEOS) to create community topology. This puts unnecessary dependency for people to setup community testbed. SONiC has cSONiC image for a long time. The project here is to incorporate cSONIC into SONiC community testbed. This will be much easier for people setup community testbed. Internship Objectives: - Setup cSONiC as neighbor devices in sonic community testbed. - Enable warm reboot LACP lag extension for cSONiC neigbhor. - Enable Macsec for cSONiC neighbor. Expected Outcomes and Deliverables: - Complete the development and setup the community testbed with cSONIC as neighbor. - Submit a pull request and upstream the code changes to the SONiC project. Recommended Qualifications: Education: Current undergraduate student. Skills & Interests: - Eager to contribute to the SONiC open-source community. - Have python/ansible experience. - Academic background in Computer Science, Computer Engineering, or a related field.

TBA
Proposal

Enhance Volcano Dashboard UX and Functionality (2025 Term 2)

Intermediate
•Varies175h (Medium)

The Volcano Dashboard serves as the frontend for displaying Volcano resources. Currently, it supports resources like Volcano Jobs, Queues, and Pods, but editing often involves raw YAML, which is not user-friendly for modifying or creating new resources. To improve user experience, this project aims to enhance the Dashboard's interactivity and user-friendliness, as well as support the display of hierarchical Queues and HyperNode resources. Expected Outcome: 1. Improve resource display and editing interfaces by providing more user-friendly interaction methods, such as using forms or visual editors instead of direct YAML editing for creating and modifying resources. 2. Support the display of hierarchical Queues and HyperNode resources with mouse-click expand/collapse functionality to clearly visualize resource relationships. 3. Optimize the user interface design to enhance aesthetics and ease of use. 4. Refactor the backend code to improve maintainability and scalability. 5. Display both key information and full information for resources, with an option to switch between views. 6. (Optional) Support the display and management of more resource types.

TBA
Proposal

Improvements to Cluster API provider for GCP (CAPG)

Intermediate
•Varies175h (Medium)

The Cluster API is a Kubernetes project to bring declarative, Kubernetes-style APIs to cluster creation, configuration, and management. CAPG provides this Kubernetes-native declarative infrastructure for GCP. The project would start with some help wanted issues around quick start and documentation, this will help with understanding mentee with CAPI/CAPG concepts and current implementation. Then we will move on to some long pending improvements documented in the issues link below.

TBA
Proposal

Open Mainframe Project 2020 Mentorship - Feilong - Ansible Module Mentorship Project

Intermediate
•Varies175h (Medium)

Create sustainable open source Ansible modules for creating/managing virtual server instances and storage devices connected to IBM Z. The final target state products could be used to communicate to various storage devices connected to mainframe and control HW function to automate storage managements. Intermediate target state would be communicating to IBM DS8K CLIs and/or RestfulAPIs to help initialization of storage device for virtual servers.

TBA
Proposal

Hyperledger - Runtime-checked automated programming for chaincode development Mentorship Project

Intermediate
•Varies175h (Medium)

Can we make ChatGPT write chaincode for us? Automated programming for other blockchain platforms is an already emerging topic, but Fabric has not been really addressed yet. This is an experimental mentorship with equal weight in research and hands-on coding, with the following goals. - To review existing examples and approaches of automated programming for smart contracts of other platforms (i.e., Solidity). - To explore the technically feasible options of automated chaincode programming for Hyperledger Fabric (incl. ChatGPT) and select one for further work. - To formulate a chaincode specification style which “seems to work well enough” on a set of representative examples with automated programming. (We don’t know yet what will work; One-shot or iterative? Requirement set or Behavior-Driven Development (BDD)? Conversational or formal specification? And so on.) - To create support for translating the specification partially or fully to runtime verification code, which can wrap the chaincode implementation. On the last point: starting from a specification is a tried and tested way to create verifier code either manually or automatically and is much easier to do correctly than creating the implementation correctly from a specification. We plan to keep this last point “classic”: i.e., no ChatGPT here. Specification-based verification criteria are usually amenable to development time verification, too (with static analysis, model checking, etc.).

TBA
Proposal

Cross Namespace Event Links (2024 Term 1)

Intermediate
•Varies175h (Medium)

One of the most requested features in Knative Eventing over the past few years has been for triggers in different namespaces than brokers, and for subscriptions in different namespaces than channels. More information can be found in the upstream issue. Expected Outcome: Knative Eventing Triggers and Subscriptions can reference Brokers or Channels in a namespace different from their own if the user possesses the necessary

TBA
Proposal

Docker Extension for Simplified Deployment (2025 Term 3)

Intermediate
•Varies175h (Medium)

OpenYurt is an open-source edge cloud-native platform designed to streamline application management in edge computing scenarios. However, the current installation process can be complex for newcomers, creating a barrier to adoption. This project aims to significantly improve the user experience by creating a Docker Extension for OpenYurt. The extension will enable users to install and configure a complete OpenYurt environment, including the yurt-dashboard, with a single click directly from the Docker Desktop interface. This will dramatically lower the entry barrier, allowing developers and edge computing enthusiasts to quickly set up a local development and testing environment, thereby fostering greater community engagement and accelerating innovation on the platform. Expected Outcome: 1. Docker Extension Development: Develop a functional Docker Extension using the Docker Extension SDK that can be installed in Docker Desktop. 2. One-Click Deployment: Package OpenYurt's core components (yurt-manager, yurt-hub, etc.) and dependencies into the extension to automate the setup of a single-node OpenYurt cluster. 3. Dashboard Integration: Provide seamless access to the Yurt Dashboard directly from the extension's UI within Docker Desktop, for example, through an "Open Dashboard" button. 4. User Guide and Documentation: Create comprehensive documentation detailing how to install, use, and troubleshoot the OpenYurt Docker Extension.

TBA
Proposal

Hyperledger AnonCreds v2 ZKP-based Credential Revocation Manager Implementation Mentorship Project

Intermediate
•Varies175h (Medium)

Hyperledger AnonCreds v2 takes the privacy-preserving features of AnonCreds v1 Verifiable Credentials to a new level. AnonCreds v2 adds support for newer, mature cryptosuites (including BBS+ Signatures), and for a number of important Zero Knowledge Proofs (ZKP) that enable an even better balance between verifiability and privacy. AnonCreds v2 also adds a crucial new, highly-scaled approach to ZKP-based credential revocation – a crucial element of almost all verifiable credential ecosystems. Called ALLOSAUR, this new scheme allows a single revocation registry to be created by an verifiable credential issuer that scales to support millions of credentials in a fast, low-data manner. Instead of sharing millions of credential revocation statuses (revoked or not), the scheme relies on the transfer of just a handful of integers between participants, enabling secure revocation without a verifiable credential holder from having to share a correlatable identifer for themself to the verifier. ALLOSAUR requires the creation of a new component in the verifiable credential ecosystem, the revocation manager, which is the goal of this Hyperledger Mentorship – to implement a scalable ALLOSAUR revocation manager. The implementation will at least be partially in Rust, with flexibility on the choice of languages/frameworks for the web service.

TBA
Proposal

Native Envoy MCP filter as replacement for ext-proc parsing (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Kuadrant's MCP Gateway uses an Envoy external processor (ext_proc) to parse MCP JSON-RPC requests, extract metadata, rewrite request bodies, and route tool calls to backend MCP servers. This works but adds latency via a gRPC hop per request and requires maintaining custom MCP protocol parsing logic. Envoy has been rapidly adding native MCP support, as of v1.38, the Envoy MCP filter can parse MCP messages, populate dynamic metadata for downstream RBAC/ext_authz filters, handle session management, support SSE and Streamable HTTP transport, and aggregate multiple backend MCP servers. A previous investigation rejected the Envoy MCP filter due to missing body modification support, limited method coverage, and no aggregation, but the filter has since evolved considerably. This project will perform a fresh evaluation, produce a design document mapping each ext_proc responsibility to native Envoy capabilities, identify gaps (particularly around request body rewriting for tool prefix stripping and dynamic metadata consumption by Authorino), build a proof-of-concept demonstrating the native filter approach, and propose an incremental migration path. The mentee will work closely with mentors on the design, validate assumptions through prototyping with standalone Envoy, and engage with both the Kuadrant and Envoy communities.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Design document covering capability mapping of each ext_proc responsibility to Envoy MCP filter features, body modification strategy, dynamic metadata vs header trade-offs for Authorino integration, federation/aggregation comparison, session management analysis, and Istio version dependency chain</p><p>&nbsp;- Proof-of-concept demonstrating Envoy MCP filter parsing requests and populating metadata, downstream authorization consuming that metadata, and tool routing to multiple backends</p><p>&nbsp;- Clear identification of what still requires custom code after migration</p><p>&nbsp;- Proposed target architecture and incremental migration plan</p><p>&nbsp;- E2E tests validating the prototype against existing test scenarios</p><p>&nbsp;- Documentation of Istio version requirements and feature gates needed</p><p><br></p>

TBA
Proposal

OCI compatible Kubernetes ontology

Intermediate
•Varies175h (Medium)

Network topologies and graph databases go hand-in-hand. The OpenAPI specifications for Kubernetes provides taxonomy, but augmenting a graph data model with formalized ontologies enables any number of capabilities, one of the more straightforward is the inferencing requisite for natural language processing, and consequently, a human-centric query / response interaction becomes becomes possible. More importantly, more advanced systems can be built when a graph data model of connected systems is upgraded to be a knowledge semantic graph. Deliverables (among other items): - MeshModel capabilities browser - Import/export of MeshModel models and components as OCI images - augmentation of cuelang-based component generator

TBA
Proposal

Open Mainframe Project 2020 Mentorship - Zowe Desktop Application State Persistence Mechanism Mentorship Project

Intermediate
•Varies175h (Medium)

Web plugins running within the application framework do not have access to a secure state persistence mechanism that would allow a user to restore one of more plugins to an early state when restarting a session. The App Framework needs to provide this capability.

TBA
Proposal

Hyperledger - Extend secure DID Registry for Hyperledger frameworks on Github/Gitlab Mentorship Project

Intermediate
•Varies175h (Medium)

A DID registry is a type of verifiable data registry that can be simply referred to as a role, a system performs to mediate the functionalities like create, verify, update, and deactivate the decentralized identifiers. The mentee will have an opportunity to learn -- The application and automation of the Decentralized Identity Hyperledger Aries and Ursa code base -- Public key cryptography -- Application of Hyperledger Ursa in enabling Zero-Knowledge proof -- Git, Shell Scripting, RUST -- Open source contribution, documentation, and sense of ownership Expected Outcome -- Command-Line utility to automate the process of creating a DID Registry for the members of organizations utilizing Github/Gitlab as Verifiable Credential Registry, On-boarding organizations, and features for easy management -- Proper test cases and documentations -- Codebase maintained with proper read me document

TBA
Proposal

Security model and processes for Kyverno

Intermediate
•Varies175h (Medium)

Improve security model and processes for Kyverno. Document security processes, help define a threat model with risks and mitigation and add best practice processes like publishing signed images.

TBA
Proposal

Improve documentation build infrastructure (2025 Term 1)

Intermediate
•Varies175h (Medium)

The build infrastructure for istio.io currently carries a complete archived copy of the site for each release of Istio. These archived versions should be separated to their own branch, with only the supported versions published. We should also separate out content which is not version-specific (e.g. the home page, news and blogs) so that only the latest version of this content is visible online. Expected Outcome: Updated publishing infrastructure for istio.io which separates evergreen content (home page, blogs) with versioned content (documentation). Drop-downs per docs page allow switching between the supported versions.

TBA
Proposal

Address findings from CNCF TAG Security & GTR assessments (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Kyverno recently completed two CNCF assessments: a security assessment by the CNCF TAG Security &amp; Compliance group and a General Technical Review by the CNCF TOC Project Reviews subproject. Together they produced a set of findings spanning documentation, threat modeling, network policies, global context cache bounds, API server authentication, SAST tooling, API stability and non-goals, UX/adopter research, webhook cert issuance/rotation guidance, "safe-mode" / temporary disable patterns, SLOs/SLIs and alerting/runbooks, dependency lifecycle and SCA workflows, third-party notices, and the security response process. The findings are tracked in umbrella issues for each assessment. In this mentorship, the mentee will work through the open findings from **both** the TAG Security &amp; Compliance assessment and the General Technical Review, propose and implement fixes across the Kyverno codebase, docs, and Helm charts, and help close out both assessments. Work includes implementing cache bounds for the Global Context, restricting Global Context access in namespaced policies, adding API server request authentication for the admission webhook, generating sample/network-policy templates and a CLI command to produce a Kyverno NetworkPolicy, integrating SAST tooling (e.g. semgrep, Nancy) into CI, updating the threat model and architecture diagrams, documenting core CRDs/API stability, webhook cert rotation, safe-mode/incident playbooks, SLOs/SLIs and reference dashboards, the SCA/dependency lifecycle workflow, and improving the security documentation on kyverno.io.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Resolve the open findings tracked in [kyverno/kyverno#15335](https://github.com/kyverno/kyverno/issues/15335) (TAG Security &amp; Compliance assessment) and [kyverno/kyverno#15473](https://github.com/kyverno/kyverno/issues/15473) (General Technical Review assessment).</p><p>&nbsp;- Implement Global Context cache bounds and access restrictions for namespaced policies (kyverno/kyverno#15359).</p><p>&nbsp;- Add admission webhook authentication of requests from the API server.</p><p>&nbsp;- Refresh the threat model (including CLI and other deployment options) and the architecture diagram to separate logical and physical components.</p><p>&nbsp;- Document core CRDs/APIs and per-API-group stability policy, webhook cert issuance/rotation guidance, recommended "temporary disable" / safe-mode patterns, SLOs/SLIs with reference dashboards/runbooks, and the end-to-end dependency/SCA workflow.</p><p>&nbsp;- Update the Kyverno security documentation: fix the audits page links, document risks of external data lookups, link to published security advisories, and link the current security response process.</p><p>&nbsp;- Add tests covering the new behaviors and document the changes in the Kyverno docs site.</p><p><br></p>

TBA
Proposal

Hyperledger - Automated Fault-Tolerant HTLC for Cross-Chain Atomic Asset Exchange Mentorship Project

Intermediate
•Varies175h (Medium)

The Hash Time Locked Contract (HTLC) is a well-known pattern for dis-intermediated asset swaps, i.e., as a mechanism to exchange assets between two parties in two different blockchain networks in an atomic manner without a trusted mediator (or trusted third party). HTLC support has been implemented in the Hyperledger Weaver Labs project, with mechanisms to lock, claim, and unlock assets supported in both the contract and higher application layers. At present, the protocol requires several manual steps by the application users carrying out the exchange or agents acting on their behalf. We would like to automate this process as much as possible by augmenting the relay module in Weaver to communicate events and trigger transactions in foreign networks; this requires both research and software development. Further, HTLC is known to have flaws that could violate system integrity properties, because it relies on parties to execute certain actions by a certain timeout or forever lose the opportunity to carry out those actions; this makes the basic protocol intolerant to system crashes. Research is needed to (provably) determine the best way to make the HTLC protocol fault tolerant, using the features of the blockchain networks maintaining the assets and the Weaver relays mediating the exchange. Augmenting the existing HTLC mechanism within Weaver will provide practical validation of this research.

TBA
Proposal

Enhancing Redis Access Efficiency and Robustness in SONiC Mentorship Project

Intermediate
•Varies175h (Medium)

*OPEN TO US BASED STUDENTS ONLY* - Accepting applications until May 23, 2025 To profile, analyze, and optimize Redis access patterns in SONiC's critical services and daemons, with the goal of reducing unnecessary Redis traffic and ensuring responsiveness even under load. Implement robust exception handling for Redis to prevent daemon crashes. Probable Implementation: Review GET/SET operations to ensure appropriate exception handling is in place. Use tools like redis-cli MONITOR, strace, perf, syslogs to identify: High-frequency Redis accesses Redundant or repeated GET/SET patterns Long response-time operations Focus on critical daemons like chassisd, pcied, lldp, syncd, orchagent. Apply the following optimizing methods for best performance: Use "HGETALL" instead of multiple "HGET" operations. Check for value-change before writing. Batching and use pipelining where it is missing. Benchmarking: Setup baseline Redis load tests and focus on couple of high CPU/mem consuming HWSkus Compare before/after metrics Redis command frequency Memory and CPU usage Expected Outcome: - High-level document outlining of existing Redis baseline, improvements required, etc. - Optimized Redis access operations - Improved exception handling for Redis reads/writes

TBA
Proposal
Showing 73 - 96 of 1243 Projects
23456