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

Automated end-to-end testing infrastructure

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)

Crossplane provides a broad library of Kubernetes custom resources that let you orchestrate systems external to Kubernetes. These include AWS S3 buckets, GCP CloudSQL instances, Azure Cosmos tables, plain old SQL databases, Helm releases, and Dominos pizzas. We call these 'managed resources'. Crossplane's goal is to allow platform teams to build their own custom resources that are in turn composed of these primitives without needing to write Kubernetes controllers in Go. Crossplane currently has extensive unit testing, but not much in the way of automated integration/e2e tests. We have a very broad surface area to test (we have around a hundred controllers that interact with cloud providers) and would like to establish some integration testing best practices so that the community can easily contribute integration tests when they work on Crossplane.

TBA
Proposal

KruiseGame cloud-hosted version development (2026 Term 1)

Intermediate
•Varies175h (Medium)

OKG has attracted many large game companies to embrace cloud-native transformation. However, for many small and medium-sized game companies, they are not familiar with the container and Kubernetes ecosystem. Due to their smaller team sizes, they have relatively weak infrastructure management capabilities. To democratize cloud-native technology for more game companies, OKG plans to launch a cloud-hosted version. Users can deploy the runtime environment with one click and complete game service integration based on the official SDK. This will reduce the complexity of using infrastructure for game companies and adapt to multi-cloud environments. - Expected Outcome: - Cloud Provider Abstraction Layer Design and Implementation - One-Click Deployment Tool/CLI Development - Official Game Service SDK Development - Multi-Cloud Environment Adaptation (AWS, Alibaba Cloud, etc.) - Simplified Configuration Management System - Comprehensive Documentation and Integration Guides

TBA
Proposal

Mapping Kubernetes Resources (2024 Term 1)

Intermediate
•Varies175h (Medium)

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. Expected Outcome: - YAML-formatted definition of one or more relationships per Kubernetes resource. - Documentation of each relationship - per component. - Development of new types of genealogies - new types of ways in which resources relate to one another and how these relationships might be visualized. - Verification of functional relationships

TBA
Proposal

Implement Tilelink Uncached Heavyweight (TL-UH) in Caravan Framework Mentorship Project

Intermediate
•Varies175h (Medium)

"Caravan: Caravan is a framework that aims to provide CHISEL Designers with an easier way to create and integrate open-source bus protocols in their designs. It is a part of SoC-Now SoC Generator where this framework is the medium for connecting bus interconnects within the design for communication of core and devices. SoC-Now that accepts parameters and generates an entire SoC consisting of a Core with selective extensions and other configuration, devices which are selected via parameters and a Bus Interconnect that is used as the communication medium between the Core and the Devices, which is also selected by means of parameters. Currently SoC-Now contains the implementation of Wishbone and Tilelink Uncached Lightweight (TL-UL). Tilelink Uncached Heavyweight (TL-UH) TL-UH is the bus protocol standardized by SiFive that is an extension of TL-UL and contains additional operations such as burst and atomic operations."

TBA
Proposal

Create an LLM app with deep understanding of a GitHub repo (2024 Term 3)

Intermediate
•Varies175h (Medium)

LLM assisted coding is one of the most promising application areas for modern AI. It will also have profound impact on open source software development. As many projects have demonstrated, "feeding" an LLM with contents from a GitHub repo will make it better at understanding coding tasks for this project. In this project, we will take a modern approach to build LLM agents based on LlamaEdge / WasmEdge, and supplement it with deep knowledge of open source projects on GitHub. The goal is for the agent to answer questions and solve problems raised by the open source community. Expected Outcome: * Build an automated tool to extract and process all files in a repo. That includes source code and docs. * develop a GitHub bot to capture all change files and update the knowledge base in real time. * generate a summary for each file (using an LLM) and supplement with its file path and other meta data. * create a vector database with the summary and original text. The vector is computed from the summary to improve search efficiency. * Run an LLM agent node with the RAG database from the repo. * Create a GitHub bot that can read new issues and respond with either an answer or a coding suggestion based on the content inside the repo. * Evaluate the answer quality.

TBA
Proposal

Per-Rule Metrics and Headlamp Plugin for node-readiness-controller (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>As clusters grow, understanding why a node is not "Ready" becomes complex. This project aims to improve visibility into the `node-readiness-controller`'s operations by enhancing its Prometheus metrics and providing a visual interface. The mentee will extend the internal metrics system to expose granular data for individual `NodeReadinessRule` objects and taint states. Additionally, the mentee will develop a plugin for Headlamp (the extensible Kubernetes UI) to visualize these readiness rules, showing real-time “node-availability” status and failure reasons directly in the dashboard.</p><p><br></p><p>Expected Outcome: New Prometheus metrics (e.g., rule evaluation duration, per-rule pass/fail counts); a functional Headlamp plugin for the project; and a pre-configured Grafana dashboard template.</p><p><br></p>

TBA
Proposal

Manage KubeArmor policies using OCI registry and use OCI hooks for container event

Intermediate
•Varies175h (Medium)

The feature aims to manage KubeArmor policies using OCI registry and use OCI hooks to get container events. Currently, KubeArmor uses a UNIX domain socket file to watch for container events, but the proposed feature aims to use OCI hooks instead. * Expected Outcome: To provide a more secure and efficient way of managing KubeArmor policies by leveraging OCI registry. Storing policies in OCI registries will make it easier to distribute policies across multiple clusters and environments. Using OCI hooks will also reduce the overhead of monitoring container events and make it easier to integrate KubeArmor with other container runtimes.

TBA
Proposal

Provide a wasm-compatible Rust TLS implementation

Intermediate
•Varies175h (Medium)

The WasmEdge networking socket API provides support for TCP and HTTP connections. But many web services today require HTTPS connections. That means we need to support TLS in WasmEdge. The Rustls crate is the most popular TLS implementation in Rust. However, Rustls is based on the Ring library, which cannot be compiled into WebAssembly. In WasmEdge, we now support the wasi-crypto spec. That allows us to compile the rust-crypto library into WebAssembly and run on WasmEdge. The goal of this project is to create a Rust TLS implementation based on rust-crypto.

TBA
Proposal

LF Networking OPNFV - Hardware Delivery Verification Tool Development and Testing Mentorship Project

Intermediate
•Varies175h (Medium)

Hardware is the base for NFV software deployment. However, it is still difficult to prepare and verify hardware in an automatic way. Based on several Operator's field trail experiences, there is a desire to verify the hardware underlying the stack / infrastructure, with this processing being automated. Initially, this verification would be carried out in labs responsible for the performance of the compliance testing, especially in the future cases examining VNF performance, where hardware will have direct impact. However, the tooling should also apply directly to larger deployments, verifying the hardware, settings, network wiring, etc., which will save valuable time for operators and users in standing up infrastructure.

TBA
Proposal

Implement security controls based on penetration testing best practices

Intermediate
•Varies175h (Medium)

Kubescape covers different hardening guidelines around Kubernetes: NSA-CISA, MITRE and CIS. Detection capabilities of potential security issues could be even more enriched by researching pen-testing tools and practices regarding Kubernetes and implementing these as controls. An example pen-test writeup is https://hacktricks.boitatech.com.br/pentesting/pentesting-kubernetes. This and others could help define a set of “offensive” controls to complement the “defensive” controls we have today. Expected Outcome: ~10 controls for detecting challenges that would commonly be found in a cluster penetration test. Documentation on how they were selected and how to use them.

TBA
Proposal

Create an MCP-based AI agent to help LF certificate prep (2025 Term 2)

Intermediate
•Varies175h (Medium)

You will create an AI agent based on open-source Large Language Models (LLMs) running on the CNCF WasmEdge runtime and an MCP server. The application will tie together key components in a modern AI agent stack to create a useful application. The AI agent will ask, answer, and explain practice questions for a specific tech certification program. It enables students to study for the certificate tests more effectively. Expected Outcome: 1. Deliverable 1: create a MCP server with 2 functions a. get_random_question(): The function selects a random question from a list. It returns both the question and the answer. This function is called by the LLM when it detects that the user asked for a new practice question. b. get_question_and_answer(): The function searches an input text from the database for an corresponding question and answer. 2. Deliverable 2: create a practice question / answer database on a subject that you are most familiar with. The MCP functions will 3. Deliverable 3: Create an agent app based on the LlamaEdge framework with a 4. Workflow 1 a. The user asks a question. The LLM calls MCP function get_question_and_answer() b. The agent adds the answer to the context c. The LLM converse with the user with knowledge about the question and its answer 5. Workflow 2 The user asks for a practice question. The LLM calls MCP function get_random_question() to get the question and answer.

TBA
Proposal

Hyperledger - DRman Utility to provision and administer DID based verifiable credential registries Mentorship Project

Intermediate
•Varies175h (Medium)

The project DRman has an end goal of developing a stand-alone utility to provision Verifiable Credential Registries [VCR]. The utility can also be used to administer the registry containing credentials issued by the organizations. The functionalities like creation, verification, modification, and revocation of credentials, form the core of this project as it enables the administrator to manage the VCR with ease. The significant aspects to be considered here are Creation, Onboarding (Enable/Restrict Access) of members, and Management(add/update/revoke) of DIDs. a) Creation (of DID Registry): Function to create a DID Registry for an organization on Git. The automation is already done for this part and can be tracked at https://github.com/DIDman/DRman/issues/3. b) Onboarding: Function to add enable/restrict access to members of an organization to a repository (e.g., using a combination of GitHub private tokens, GitHub username & users DID). c) Manage: Function to list APIs that are needed to add/update/revoke access DID’s or (DID Document) saved as files on the repo. This summer, the project holds a variety of interesting automation issues to be addressed that focus more on onboarding and management of the organizations that intend to add themselves to the DID-based Verifiable credential registry.

TBA
Proposal

Hyperledger - Chia Connector for Hyperledger Cactus Mentorship Project

Intermediate
•Varies175h (Medium)

Develop a Cactus Chia connector plugin + test infrastructure (container images, container manager class, etc.) from scratch. Include end to end test cases powered by Jest and the said testing infrastructure that prove that the connector is working as intended with a locally simulated Chia network. You will be creating a new package in the Cactus monorepo from scratch under the packages/cactus-plugin-ledger-connector-chia/ path. All the information presented here can also be found at the GitHub issue tracker of Hyperledger Cactus, filed under issue #1634 => github.com/hyperledger/cactus/issues/1634

TBA
Proposal

Hyperledger Fabric - Distributed Citizens Pulse Platform For State/City Council Mentorship Project

Intermediate
•Varies175h (Medium)

Introduction and Problem Statement: Many city councils want to know the voice of citizens whenever a change is implemented. Usually when a city approves a plan, there are always a small minority affected/opposing it.The city always wants feedback from the citizens on their decisions and they never have a proper channel to do so. Though the usage of online forums are common in developed and developing countries, its usually challenging to get public agree on a common platform as the platforms are controlled by individual companies/government bodies. Also, public is worried about privacy and safety of the platform. Further, there are also situations like some NGOs who host the platform have financial challenges and hence discontinue their services. Proposed Solution: In a distributed platform like Hyperledger, its possible to decentralize the ownership. This gets to a situation where the platform is by the people and for the people. Also, due to the immutable nature of the Hyperledger, there is one source of truth existing in the system. The Endorsement policies handle the privacy part and Certificate-Authorities provide safe and secure platform. When the Hyperledger components are shared among the NGOs/government/Universities/private-bodies, the ownership is distributed.

TBA
Proposal

Non K8s KubeArmor Enhancements (2024 Term 3)

Intermediate
•Varies175h (Medium)

Extend KubeArmor features to non-Kubernetes environments by implementing karmor recommend for host policies and unorchestrated containers, and enabling dynamic configuration for default posture and visibility through kubearmor.yaml, a new gRPC service, and karmor commands. Enhance karmor profile for host logs, support karmor install for VMs, and validate policies for non-Kubernetes setups. Expected Outcome: User friendly KubeArmor functionality including Application Behaviour and Policy Management in non-Kubernetes environments.

TBA
Proposal

Workflow engine (extended)

Intermediate
•Varies175h (Medium)

Integrate a new architectural component into Meshery: a workflow engine. This project involves shifting Meshery off of bitcask and off of sqlite over to postgres using gorm (golang). Interns will familiarize with concepts of orchestration engines, including chaining workflows, and content lifecycle management.

TBA
Proposal

Support multi-clusters (2026 Term 1)

Intermediate
•Varies175h (Medium)

Kmesh, as a high-performance service mesh data plane, is now only supported for use in a single cluster. However, now that multi-cluster support for istiod has been realized, we are able to move forward with the multi-cluster adaptation of Kmesh to support the use of Kmesh in multi-cluster environments. Adaptation to the current multi-cluster production environment with LLM and large data. - Expected Outcome: - 1.Code for implementing the Kmesh multi-cluster feature - 1.1. Adapting to the Istio Multi-Cluster Function API - 1.2. Traffic Management in multi-cluster scenarios - 1.3. Use IPsec to ensure the security of node communication. - 2.userguide doc - 2.1. proposal - 2.2. userguide - 3.e2e test - 3.1. Unit Test of Feature Function - 3.2. E2E test code

TBA
Proposal

Tooling for detecting impact of behavioral changes in Go lib (2026 Term 1)

Intermediate
•Varies175h (Medium)

Maintenance of a stable Go library often involves value-judgement calls regarding what changes can impact downstream consumers. While some existing tooling like apidiff can go some way towards preventing breakage, these tools work purely in terms of API-level breakage such as changing the type of a symbol. Inspired by tooling in other language ecosystems such as Rust this proposal sets out to build a tool that can give statistical information about the impact of any change on downstream consumers by running the build pipelines and test suites of dependents before and after a particular change. This would empower maintainers to make better informed choices about changes and foster an ecosystem. We think this is specially important for the OpenTelemetry project since the OpenTelemetry Go modules and the OpenTelemetry Collector modules are foundational modules used within the CNCF on other projects (e.g Kubernetes, Jaeger) as well as outside of it. The intent is to build a tool that could be used as well by other CNCF projects since Go is the *lingua franca* of the foundation, enabling all projects to have a flourishing ecosystem. - Expected Outcome: We would like to have a tool written in Go that is able to (i) gather all publicly-listed dependencies of a module, (ii) safely run the test suite of dependencies for a given version of the code and (iii) compare two test suites and provide a statistical summary of the differences between the two to help in decision-making.

TBA
Proposal

LF Networking ONAP - Modeling/etsicatalog Mentorship Project

Intermediate
•Varies175h (Medium)

The Modeling/etsicatalog project provides VNF/PNF/NS package management service by Micro Service. It also includes a TOSCA parser service which provides generic parser service. As the unified run-time catalog, its VNF/PNF/NS package management interfaces align with SOL003/005 specification. Etsicatalog is a standalone web application based on Python3 and DJango framework. Etsicatalog is going to support SDC Subscription/Notification functions in Guilin version. SDC is the most important design-time component of ONAP. The mentee will be required to make the technical research and take part in the development related this function under the guide of our team. Some work on Alignment with SOL specification for API is also required for the mentee. Besides, We will consider the support for CNF which is a stretch goal (need volunteer)alignment with the CNF task force where applicable.

TBA
Proposal

Document technical outcomes on website (2025 Term 2)

Intermediate
•Varies175h (Medium)

On the Cilium homepage (https://cilium.io/), we want to document technical outcomes from using Cilium. Think of these technical outcomes as aggregating some of cilium features to achieve a high level technical goal. These are the current ones we have in mind: Zero Trust Networking, Network Automation, Distributed Firewalling, Cost and Carbon Savings, Multi-cloud Connectivity. Expected Outcome: A section of the Cilium website detailing these technical outcomes. This section on the website can include any supporting materials from the Cilium community i.e blogs, videos, talks, illustrations, etc.

TBA
Proposal

Develop E2E dashboard with CI/CD pipeline details and enhance litmus e2e website

Intermediate
•Varies175h (Medium)

his project aims to build an E2E Web dashboard that will display the CI/CD pipeline details of [scheduled](https://litmuschaos.github.io/litmus-e2e/generic-pipeline/pipeline-runs/pod-level-run.html) and [manual](https://github.com/litmuschaos/litmus-e2e/tree/master/.github/workflows) runs. It should contain all the litmus backend and portal pipelines and can be easily switched or add more pipelines. Currently, [these](https://github.com/litmuschaos/litmus-e2e/tree/master/.github/workflows) are the pipeline present in the e2e.

TBA
Proposal

Automated Documentation Sync Bot for Krkn-Chaos Projects (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>The krkn-chaos/website repository hosts the unified documentation for the entire krkn-chaos ecosystem (krkn, krkn-hub, krknctl, krkn-ai, krkn-operator, cerberus, etc.) as a Hugo/Docsy site deployed at krkn-chaos.dev. Currently, when changes are made to any of these upstream projects — such as adding a new scenario, modifying configuration options, or updating CLI flags — someone must manually open a PR against the website repo to update the corresponding docs. This is tedious, easy to forget, and often leads to documentation drift where the docs no longer match the actual tool behavior. This issue proposes building a bot or GitHub Action-based workflow that detects documentation-impacting changes in upstream krkn-chaos repositories and automatically creates a draft PR on the website repo with the relevant documentation updates. The bot would analyze the scope of the change (e.g., new config fields, updated parameters, new scenario) and generate or update the corresponding Hugo content files, following the existing content structure and conventions (tabbed scenario layouts, parameter tables, etc.).</p><p><br></p><p>Expected Outcome:&nbsp;</p><p>&nbsp;- Build a GitHub Action or bot that triggers on merged PRs in upstream krkn-chaos repos and automatically creates draft documentation PRs on the website repository following existing Hugo/Docsy content conventions.</p><p>&nbsp;- Support common change types including new or updated config fields, CLI flag changes, new chaos scenarios, and modified parameter tables.</p><p>&nbsp;- Enable interactive refinement of generated documentation PRs through review comments, similar to code review bots like CodeRabbit.</p><p><br></p>

TBA
Proposal

Plugin-level Cache and Nominator Shared Across Scheduler Profiles (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Today most Koordinator scheduler plugins (DeviceShare, NodeNUMAResource, Reservation, etc.) keep their own private cache per scheduling framework/profile, so configuring multiple profiles in a single `KubeSchedulerConfiguration` produces duplicated plugin caches even though the upstream `SchedulerCache` and `PodNominator` are singletons per scheduler instance. This duplication wastes memory, desynchronizes state across profiles, and exposes correctness bugs: in `RunFilterPluginsWithNominatedPods`, `AddPod` is invoked for pods that are still in scheduling and are therefore missing from `nodeDeviceCache`'s used map, which causes DeviceShare and NodeNUMAResource to fail to reserve resources for high-priority pods in RDMA / VF / NV-Switch scenarios. This project will introduce a unified plugin-level Cache and Nominator abstraction that is shared across all profiles in the same scheduler instance, correctly integrates with `Reserve` / `UnReserve` lifecycle hooks, and fixes the `AddPod` / `RemovePod` handling for high-priority device and NUMA workloads.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- A shared plugin-level `Cache` and `Nominator` framework exposed to Koordinator scheduler plugins, with a lifecycle tied to the scheduler instance rather than individual profiles</p><p>&nbsp;- Migration of DeviceShare, NodeNUMAResource, and Reservation plugin caches to the shared implementation, removing per-profile duplication</p><p>&nbsp;- Correct `AddPod` / `RemovePod` handling via reused `Reserve` logic that records assignment placements in the nominator, cleared symmetrically on `Reserve` / `UnReserve`</p><p>&nbsp;- Regression and stress tests covering multi-profile scheduling, preemption with nominated pods, and high-priority RDMA / VF / NV-Switch device assignment</p><p>&nbsp;- Developer documentation describing the shared Cache / Nominator API and migration guidance for other plugins</p><p><br></p>

TBA
Proposal

Add GPU support to Cluster API Provider 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. This project would focus on adding support for attaching GPUs to instances used for worker nodes in a Kubernetes cluster created by CAPG.

TBA
Proposal
Showing 361 - 384 of 1243 Projects
1415161718