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
13453 Projects Found
Sort by

Karmada Self-Signed Certificate Content Standardization (2025 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)

In the existing Karmada architecture, each component should have its own unique certificates to ensure clear identity and security. Best practices dictate that each component's name be used as the Common Name (CN) in its certificate to facilitate identity differentiation. However, currently, all Karmada components share same identical certificate content, leading to confusion and potential security risks. The objective of this project is to enhance the compliance of the Karmada certificate system by ensuring that each component possesses distinct certificates that reflect its identity. This will improve system security, reduce management complexity, and align with industry standards. This project aims to achieve the following standards: 1. Utilize a single CA certificate for the entire Karmada system. 2. Issue individual server certificates for each server component, using the component name as the CN. 3. Issue individual client certificates for each client component, using the component name as the CN, same client can use consistent certificate for different servers. Expected Outcome: 1. Complete the issuance of different certificates for 8 server components and import the certificate content into the corresponding certificate Secrets. 2. Complete the issuance of different certificates for 11 client components and import the certificate content into the corresponding certificate Secrets or Config Secrets.

TBA
Proposal

Tremor - Modular sub-queries in tremor-query

Intermediate
•Varies175h (Medium)

Currently tremor supports composition through composing pipelines together, through function composition and through allowing references to query operator definitions and constants in externalizable modules that can be loaded via a module path. It would be excellent if the modularity in tremor extended fully to the query language so that distinct subgraphs could be modularized and consumed by multiple queries to optimise for reuse of flow oriented logic in tremor. This would require extending module support in the tremor query language to support sub-graph definitions with parameters that can be declared and used as part of a higher level query. Modules in tremor-query in their current state: <https://docs.tremor.rs/tremor-query/modules/> This project idea involves designing the sub-graph module syntax and semantics and implementing changes to the lexer, grammar, optimizers and runtime. It is most suited to candidates who are interested in programming language evolution and design.

TBA
Proposal

LF Networking ONAP - ETSI NFV APIs Conformance Test for OVP Mentorship Project

Intermediate
•Varies175h (Medium)

Now VTP as the VNF test platform can support OVP VNF compliance and validation test. It can manage and orchestrate different VNF testing scenario across different SUT environment like ONAP MANO, OpenStack Cloud, Vendor VNFM, SDN Controller, etc under one umbrella across different Test providers and partner labs. As the open source test platform, it should include standard test case from standard organization, so that it can support the testing for standard component which can accelerate OVP test and certification process for commercial products implemented by reference standards. VTP is going to support ETSI NFV APIs conformance test. The mentee will be required to make the technical research and develop related test cases and integrate with VTP under guide of our team.

TBA
Proposal

Scalability testing for Kyverno

Intermediate
•Varies175h (Medium)

Define and execute scalability tests for Kyverno on large Kubernetes clusters with several namespaces and resources. The candidate has to propose and execute a performance test plan and help optimize resource usage of Kyverno for different loads for large Kubernetes clusters.

TBA
Proposal

Streamlining Microcks Deployment on AWS Marketplace (2025 Term 1)

Intermediate
•Varies175h (Medium)

Microcks is a cloud native, open source tool under CNCF for API and microservices mocking and testing. This project focuses on creating a validated and repeatable SaaS architecture for deploying Microcks on AWS, with the ultimate goal of listing it on the AWS Marketplace through the AWS Partner Network Co-Sell program. By addressing the community's frequent demand, this initiative will simplify Microcks' adoption while leveraging a complete suite of AWS services to ensure scalability, security, and ease of deployment. The core Microcks maintainers focus on features, security, and enhancements. The adopters are responsible for production setups. However, a shared repository of best practices can help users learn from one another in a true open-source spirit. Participants will contribute to the Microcks community repository by documenting the AWS Marketplace deployment. Expected Outcome: Enable Microcks adopters to confidently deploy production-ready setups on AWS, ensuring the scalability and reliability needed for enterprise environments. By integrating Microcks into the AWS Marketplace, the project will further enhance its visibility and adoption within the AWS ecosystem. - Designing and validating a SaaS architecture that is compliant with AWS Foundational Technical Review (FTR). - Utilizing AWS-native services such as EKS, Aurora (PostgreSQL), DocumentDB, API Gateway, IAM, and CloudFormation for an end-to-end deployment. - Streamlined deployment workflows

TBA
Proposal

Implement Binding Policy Frontend with Backend Endpoints (2025 Term 1)

Intermediate
•Varies175h (Medium)

This project focuses on developing the UI components necessary for managing Binding Policies in KubeStellar. Users should be able to create, update, delete, and view policies via an intuitive interface while ensuring seamless integration with the backend API. Objectives: - Develop UI components for managing Binding Policies (CRUD operations). - Implement validation mechanisms to ensure policies comply with Kubernetes standards. - Provide real-time updates on policy status and binding information. - Improve UI design for a seamless user experience. Expected Outcomes: - A fully functional Binding Policy management UI. - Smooth user interaction with the backend API. - Modern UI with real-time validation and feedback.

TBA
Proposal

Adaptive Sidecar Resources in SidecarSet (2025 Term 3)

Intermediate
•Varies175h (Medium)

SidecarSet is an advance workload for sidecar container injection and upgrade. Currently the sidecar container resource must be set explicitely in the sidecar template, however in the cases of traffic proxy, log collection and device emulation etc, it is desirable to to set the resources according to resource of app container. The goal is to support the adaptively setting for sidecar resources and provide best practice for typical use cases. Expected Outcome: 1. Implementation for adaptively resources setting for sidecar in SidecarSet workload 2. Unit and integration tests 3. Documentation for the function usage and typical use cases in the OpenKruise website

TBA
Proposal

Test enhancements: Kyverno CLI tests with envtest/fake client (2026 Term 1)

Intermediate
•Varies175h (Medium)

The Kyverno CLI should be flexible enough to perform real variable substitutions when CEL libraries are used in policies, in addition to static substitutions. This enhancement would enable comprehensive policy testing without requiring a real Kubernetes cluster, significantly speeding up development and CI/CD pipelines.

TBA
Proposal

Web Redesign of Feature Comparison

Intermediate
•Varies175h (Medium)

Cloud Native Buildpacks is a specification and set of tools that help you take source code and convert them into OCI images. Sound familiar? Maybe you've heard of Docker, Source-2-Image, Kaniko, etc. Well you are not alone. The goal of this project is to refactor our existing ["features" page](https://buildpacks.io/features/#comparison) to provide an easier to comprehend comparison across other similar solutions. Through this project, you'll research each alternative, learn how they compare and aim to provide that information to the users in an easy to digest format. This will include designing and implementing a better format to compare projects and their features side-by-side.

TBA
Proposal

Improve lifecycle management of sandbox monitors (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Currently, urunc launches sandbox monitors, such as Firecracker and QEMU</p><p>through command-line invocations. This approach offers limited control over the</p><p>sandbox lifecycle once the process is started. On the other hand, most</p><p>monitors expose remote management interfaces, typically through a socket-based</p><p>API.</p><p><br></p><p>These interfaces provide access to the same operations currently performed via</p><p>CLI, but also enable further control over the sandbox lifecycle. In particular,</p><p>they allow more fine-grained lifecycle management of the sandbox, including</p><p>querying and monitoring its state, performing device hotplug and unplug</p><p>operations and interacting with the guest.</p><p><br></p><p>This project aims to extend urunc's sandbox integration layer to support remote</p><p>management interfaces and to explore each monitor's capabilities in order to</p><p>extend the functionalities of urunc sandboxed containers.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- A design document describing the updated architecture and workflow for</p><p>&nbsp;&nbsp;spawning and managing sandbox monitors in urunc.</p><p>&nbsp;- Implementation of the necessary changes in urunc to manage sandbox monitors</p><p>&nbsp;&nbsp;through their respective APIs.</p>

TBA
Proposal

Implement component-model proposal in WasmEdge

Intermediate
•Varies175h (Medium)

The component-model proposal merges and supersedes the Module Linking and Interface Types proposals. With this feature, WasmEdge can execute multiple modules wasm with Module Linking and and more flexible types with Interface Type.

TBA
Proposal

Package Meshery Catalog Artifacts as OCI Images

Intermediate
•Varies175h (Medium)

Meshery (https://meshery.io) is a self-service engineering platform, Meshery enables collaborative design and operation of cloud native infrastructure. [Meshery Catalog](https://meshery.io/catalog) content represents a schema-based description of cloud native infrastructure. Catalog content need to be portable between Meshery deployments as well as easily version-able in external repositories. - Expected outcome: Rebuild the Meshery Design System so that it provides the open source building blocks to design and implement consistent, accessible, and delightful product experiences.

TBA
Proposal

Reduce Helm chart initContainers reliance (2025 Term 2)

Intermediate
•Varies175h (Medium)

This project aims to investigate and implement ideas for improving KubeStellar Core Helm chart reliance by contributing improvements to Helm project and reducing its reliance on initContainers for waiting/gathering/processing Kubernetes resources that are used by other containers (for example, KubeFlex Control Planes and their kubeconfigs). 1. Introduce an annotation that would make Helm wait for user- specified resources 2. Introduce priority/coordination of Helm resource creation 3. Introduce an alternative path for dependence chart override values 4. Introduce a mechanism for a chart to require a specified Helm min version or range 5. Introduce an alternative to kubectl initContainers Expected Outcome: 1. A comprehensive investigation of potential alternative methods and approaches 2. Contributions to Helm project to introduce new features that would allow to improve the quality of KubeStellar Core chart 3. A solution implementation that reduces the reliance on kubectl initContainers

TBA
Proposal

Strengthening Security through Fuzz Testing

Intermediate
•Varies175h (Medium)

Enhance Islet’s security by identifying vulnerabilities early using fuzz testing. This project integrates Cargo Fuzz tools with Islet’s CI pipeline, focusing on testing RMM interfaces (RMI and RSI) based on ARM’s RMM specification. Expected Outcome: Deliver a set of robust fuzz tests integrated into Islet’s CI, improving security and compliance with ARM standards.

TBA
Proposal

Proof of concept making multiarch images with buildkit (2024 Term 1)

Intermediate
•Varies175h (Medium)

A proof of concept to add buildkit support to pack in order to build multi-arch images. Pack is the reference implementation of a Cloud Native Buildpacks platform used to build application images from source code. Expected Outcome: Multi-arch support has been one of the most requested features for Cloud Native Buildpacks, and this would allow end-users/developers to build multi-arch images with the pack cli.

TBA
Proposal

Implementing the resiliency score feature (2025 Term 3)

Intermediate
•Varies175h (Medium)

The idea is to define criteria to measure the resiliency score of a cluster after a set of chaos scenarios. Expected Outcome: - a page in our documentation website clearly explaining the scoring algorithm implemented and the best practices to leverage it on the user's environment - a set of functions in our API library to easily collect data and calculate the score - the implementation of the scoring method across all Krkn scenarios, and an update to our telemetry data structures to include the resiliency score to allow the collection by downstream observability systems

TBA
Proposal

Metrics for TCP Long Connection (2025 Term 1)

Intermediate
•Varies175h (Medium)

Currently, Kmesh metrics are only reported when a TCP connection is closed. In the case of long connections, it is not possible to know the status before the connection is closed. Therefore, we hope to add the capability to periodically report metrics for long connections. Expected Outcome: 1. proposal 2. code 3. user guide

TBA
Proposal

Add Agones to Headlamp - Game Server Management UI (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Agones is a Kubernetes-native platform for hosting, running, and scaling dedicated game servers. This project builds a Headlamp plugin that adds an **Agones** section to Headlamp, surfacing Agones CRDs so operators can **view and manage game servers, fleets, and allocations** from the Headlamp UI. The plugin follows Headlamp UX patterns with list and detail views, links between related resources, and visibility into lifecycle and allocation state.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Plugin exposes key Agones CRDs: GameServer, Fleet, GameServerSet.</p><p>&nbsp;- List views, with summary columns (name, namespace, state, address, port, node, replicas).</p><p>&nbsp;- Detail pages, showing config, status conditions, lifecycle state, and sub-resources (game server pods).</p><p>&nbsp;- Relational navigation, fleet → game servers; game server → fleet.</p><p>&nbsp;- Consistent Headlamp UX, icons, tables, detail layouts, Map view enhancements.</p><p>&nbsp;- Structured config display (collapsible sections/YAML toggle), humanized lifecycle states (Ready, Allocated, Shutdown).</p><p>&nbsp;- README with prerequisites and limitations; blog post demoing usage.</p><p><br></p>

TBA
Proposal

Support piper as a new backend of the WASI-NN WasmEdge plugin (2024 Term 2)

Intermediate
•Varies175h (Medium)

WasmEdge supports PyTorch, TensorFlow Lite, llama.cpp, and more NN backend. Dealing with the text-to-voice is a big thing that we want to achieve. To make it possible, we would like to integrate piper (https://github.com/rhasspy/piper), A fast, local neural text-to-speech system in C++ as a new WASI-NN backend (https://github.com/second-state/wasmedge-wasi-nn). Expected Outcome: 1. A new plugin provides a piper WASI-NN backend 2. A test suite for validating the plugin 3. Documents and examples for explaining how to use the plugin.

TBA
Proposal

Multi-Architecture Builds Support

Intermediate
•Varies175h (Medium)

The rise of ARM processors has created new binary targets for pre-compiled executables. Additionally, there are tales of widespread use of operating systems that aren't linux? In the ideal case a `pack` user could create a build for an abritrary architecture and operating system, regardless of the host system they used to run the command. Expected outcome: Improved multi-architecture (including ARM) and multi-os "cross-compilation" support in [pack](https://github.com/buildpacks/pack/) Upstream Issue (URL): https://github.com/buildpacks/pack/issues/1459 and https://github.com/buildpacks/pack/issues/1460

TBA
Proposal

Jaeger-V2 Observability (2024 Term 1)

Intermediate
•Varies175h (Medium)

Jaeger is a distributed tracing platform. Jaeger V2 is a major new version where we rebase all Jaeger backend components (agent, collector, ingester, and query) on top of the OpenTelemetry Collector. Currently jaeger-v2 components are initialized without observability clients. We need to instantiate appropriate logging, tracing, and metrics clients and pass them to the components. The existing code uses internal metrics API, which needs to be bridged to OTEL metrics to minimize code changes. Expected Outcome: Achieve parity in observability of jaeger-v2 compared to jaeger-v1

TBA
Proposal

OpenCost Data Model 2.0 (2025 Term 3)

Intermediate
•Varies175h (Medium)

OpenCost's data model is now 6 years old, and we have learned a great deal long the way. Based on these learnings, we would like to revamp how OpenCost represents its cost and usage data across the stack. We want to set OpenCost up for the next set of features and scale by building a solid foundation for the way we represent data. Expected Outcome: We would make the UID of Kubernetes objects into a first class citizen. These UID based objects would then be grouped in a similar hierarchy to the way Kubernetes itself is organized. A successful conclusion of this project would see an additional emitter implemented in OpenCost, that emits data objects stored in compressed protobuf which reflect a hierarchy of Kubernetes objects. The mentors will help establish this hierarchy. This hierarchy should then be tested via integration tests against the existing objects, and key metrics compared to be equal across those.

TBA
Proposal

Extend Support Matrix and Document Usecases

Intermediate
•Varies175h (Medium)

The project aims to extend KubeArmor support and document how KubeArmor is relevant for securing Kubernetes on Edge in addition to generic Kubernetes based Application deployments - Expected Outcome: - Try KubeArmor on Different Kubernetes Platforms - Microshift, k0s - Make fixes to deployments to make them work if needed - Document Usecases on these platforms - Document Usecases at a broader level for EDGE and Container Security - Produce Blogs about extended support and additional usecases

TBA
Proposal

Add Strimzi to Headlamp: Kubernetes Kafka management UI (2026 Term 1)

Intermediate
•Varies175h (Medium)

Strimzi is a Kubernetes Operator for running Apache Kafka. This project builds a Headlamp plugin that adds a **Strimzi** section to Headlamp, surfacing Strimzi CRDs so operators can **view and manage Kafka clusters, topics, users, and connectors** from the Headlamp UI. The plugin follows Headlamp UX patterns with list and detail views, links between related resources, and optional metrics embedding. - Expected Outcome: - Plugin exposes key Strimzi CRDs: Kafka, KafkaTopic, KafkaUser, KafkaConnect, and KafkaConnector. - List views, with summary columns (name, namespace, brokers, partitions, replication, status). - Detail pages, showing config, status conditions, sub-resources (broker pods, connectors), and basic actions (create/edit topic, regenerate user creds). - Relational navigation, cluster → topics/users; topic → cluster. - Consistent Headlamp UX, icons, tables, detail layouts, Map view enhancements. - Structured config display (collapsible sections/YAML toggle), humanized statuses, validated forms for mutating actions. - README with prerequisites and limitations; blog post demoing usage.

TBA
Proposal
Showing 12457 - 12480 of 13453 Projects
518519520521522