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

Create a search-enabled API server for local LLMs (2024 Term 2)

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)

WasmEdge is a lightweight inference runtime for AI and LLM applications. The LlamaEdge project (https://github.com/LlamaEdge) has developed an OpenAI-compatible API server (https://github.com/LlamaEdge/LlamaEdge/tree/main/api-server) and a server-side RAG app (https://llamaedge.com/docs/user-guide/server-side-rag) based on WasmEdge. In this project, we aim to use the LlamaEdge components to build a new API server that incorporates real-time Internet search results into LLM answers. Expected Outcome: An OpenAI-compatible local LLM API server that uses Google Search for supplemental context

TBA
Proposal

Documentation assessment

Intermediate
•Varies175h (Medium)

Description: Gateway API is an evolution of Kubernetes Ingress and Service networking that aims to upgrade and improve these APIs. This project is to have a docs assessment performed, to help us come with a plan for improving our documentaion. In particular, we're looking for someone to look at the content organization, the clarity of the language and concepts, and to make sure it's as readable as possible for both implementors and end users. You'll be working with the mentors and maintainers of the project, with a stretch goal being to make the changes you produce in the initial assessment.

TBA
Proposal

Controller HA (Active/Standby) Support (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Add Active/Standby HA support for the KubeSlice Controller.</p><p>&nbsp;- Leader election: Only one controller cluster (the “Active” node) holds a distributed lock (e.g., a Lease) and is permitted to write updates to worker clusters or manage Slice configurations.</p><p>&nbsp;- Constant state sync: The Standby cluster continuously mirrors the Active cluster’s state, including relevant KubeSlice CRDs (Slices, ServiceExports, Clusters, etc.).</p><p>&nbsp;- Heartbeating: The Standby cluster monitors the health of the Active cluster.</p><p>&nbsp;- Failover: If the Active cluster fails to renew its lease, the Standby cluster detects the timeout, acquires the lock, promotes itself to Active, and worker clusters are updated to use the new Active controller.</p><p><br></p><p>Expected Outcome: Implement an Active/Standby HA architecture that makes the KubeSlice management plane resilient and disaster-recovery-ready.</p><p><br></p>

TBA
Proposal

Enterprise Ready OpenCost: Integration Testing (2025 Term 2)

Intermediate
•Varies175h (Medium)

We need enhanced integration tests to prepare OpenCost for graduation and enterprise readiness. This proposed project will deliver a comprehensive suite of integration tests designed to facilitate development and contribution by third parties, while protecting the stability of OpenCost for our tens of thousands of users. These tests will validate both the quality of the data collected by OpenCost, and the correct operation of the APIs. We have recently implemented a pipeline that builds real stacks for these tests to hit - we now need to fill that framework up with great tests. See the testing strategy document @ https://github.com/opencost/opencost/blob/develop/docs/testing/AUTOMATED_TESTING.md for the current state of testing, and the infrastructure that we have put into place to support this mentorship effort. Expected Outcome: 1) A comprehensive integration test suite as defined in the linked ticket. 2) All tests run and pass automatically in pre-existing per-push integration test pipeline. 3) Approach for each integration test is documented 4) Endpoint coverage % and parameter coverage % is calculated 5) Any unfinished or follow on work is documented via issues on OpenCost

TBA
Proposal

Enhancements around Kubernetes performance testing (2026 Term 1)

Intermediate
•Varies175h (Medium)

We intend to get some help around open issues in the repository and also come up with new use cases and scenarios for performance testing any kubernetes distribution. We love new perspectives and are always open to new ideas alongside what we have as tracked work in github issues. For the purpose of this mentorship program term, we have created an umbrella issue that outlines some of the critical enhancements to the project. - Expected Outcome: To knock down some of open critical issues and bring in new perspective to the project. There are no restrictions while working with issues/enhancements.

TBA
Proposal

CoRIM Profiles Refresh

Intermediate
•Varies175h (Medium)

Description: Update the CoRIM profiles used for provisioning Veraison services to align with the most recent specifications. Expected Outcome: - Add support for the updated formats to the `veraison/corim` package - Add support for the updated formats to the `veraison/cocli` command line tool - Allow the provisioning of endorsement and reference values specified using the updated formats to `veraison/services`

TBA
Proposal

Hyperledger - Solang Solidity Compiler optimizations and error handling Mentorship Project

Intermediate
•Varies175h (Medium)

Solang is a Solidity compiler that targets several blockchains, including Solana, Substrate and ewasm. The mentorship project consists of three goals that can provide mentees with a broad knowledge of a compiler's inner-workings. The three tasks are in different stages of the compiler. Solang’s parser analysis halts compilation entirely when there is any invalid expression or function declaration. This should be improved so that it continues parsing the Solidity contract after encountering an error, providing better diagnostics (warnings and errors) to the developer. The parser utilizes Lalrpop and the mentee would be using its error handling capabilities to implement a solution. Often the length of a dynamically allocated array is known at compile time as the allocation happens with a constant. When the length is required at some later point (e.g. for bounds checks for array indexing), the length is retrieved again. Mentees will add an optimization to make the length a compile time constant. Solang has an implementation of multiplication of integers of 256 and 128 bit. This does not have overflow detection. This requires improving the multiplication in the solang stdlib.

TBA
Proposal

Implement AccessPolicy CRD for tool-level authorization (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Kuadrant's MCP Gateway is an Envoy-based gateway for Model Context Protocol (MCP) servers. It currently handles authentication and coarse-grained authorization via AuthPolicy/Authorino, but has no built-in mechanism for tool-level authorization, e.g., allowing agent A to call `add` and `subtract` on a math server while agent B can only call `subtract`. The kube-agentic-networking SIG is defining a standard AccessPolicy CRD for exactly this. MCP Gateway is well-positioned to implement it because its ext_proc already parses MCP request bodies and exposes tool metadata via headers (`x-mcp-method`, `x-mcp-toolname`, `x-mcp-servername`). This project will design how AccessPolicy maps to Kuadrant's AuthPolicy/Authorino, then build an experimental implementation covering CRD definition, a controller that translates tool-level authorization rules into Authorino configuration, identity model integration (starting with OIDC), `tools/list` response filtering so callers only see tools they're authorized to use, and CEL-based authorization expressions. The mentee will work closely with mentors on the design doc, pair on implementation decisions, and engage with both the Kuadrant and kube-agentic-networking communities.</p><p>- Expected Outcome:</p><p>&nbsp;- Design document covering AccessPolicy-to-AuthPolicy/Authorino mapping, body parsing strategy (ext_proc vs Envoy MCP filter), identity model choices, `tools/list` filtering, and CEL-based authorization</p><p>&nbsp;- AccessPolicy CRD with status conditions and CEL validation rules</p><p>&nbsp;- Controller that watches AccessPolicy resources and generates/updates AuthPolicy resources with authorization rules based on `x-mcp-toolname` headers</p><p>&nbsp;- OIDC identity source support, with consideration for ServiceAccount and SPIFFE identity types</p><p>&nbsp;- `tools/list` response filtering so callers only see tools they are authorized to invoke</p><p>&nbsp;- CEL-based authorization rule support (e.g., `request.mcp.tool_name.startsWith("read_")`)</p><p>&nbsp;- E2E tests covering allow/deny scenarios for tool-level access control</p><p>&nbsp;- Documentation guide in `docs/guides/`</p><p><br></p>

TBA
Proposal

Develop an FAQ Chatbot for Vitess using Retrieval-Augmented Generation (2025 Term 1)

Intermediate
•Varies175h (Medium)

Vitess is a distributed database system built on MySQL. Developers often need to search through documentation, Slack discussions, and GitHub issues to find answers. This project will implement an AI-powered FAQ chatbot using **Retrieval-Augmented Generation**, integrating **vector search** with an **LLM** (like OpenAI, DeepSeek, GPT-4, Mistral, Llama3). The chatbot will be available via a **CLI and Slack bot** for developer support. Expected Outcome: A chatbot that provides accurate Vitess-related answers via CLI and Slack, using indexed documentation and discussions for retrieval.

TBA
Proposal

Workflow engine

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

CAPA Reimagining how we handle AWS account preparation

Intermediate
•Varies175h (Medium)

Description: Cluster API Provider AWS (CAPA) can create and manage the lifecycle of Kubernetes clusters in AWS (with the help of Cluster API in general). For each target AWS account where a user wants to create clusters it must be prepared for usage first. This is currently done using [clusterawsadm](https://cluster-api-aws.sigs.k8s.io/topics/using-clusterawsadm-to-fulfill-prerequisites.html) which creates/updates a CloudFormation stack that in turn creates/updates IAM resources. This approach has caused issues as CloudFormation is region specific but IAM is global and users often run the tool in different regions which results in failed stacks that cannot easily be deleted. As a project we want to move away from using CloudFormation and instead use API calls (like the rest of CAPA). We also want to make the process idempotent so it doesn't matter if you run it against different regions. This account preparation is key to CAPA and with out it CAPA cannot run. Expected Outcome: A new approach to handling the prerequisites required for CAPA. We need to continue to support the cli based approach (so clusterawsadm will be updated) but we can also explore a declarative approach with an operator.

TBA
Proposal

Wiz Scanning Support (2025 Term 2)

Intermediate
•Varies175h (Medium)

Copacetic currently doesn't support vulnerability scan reports by Wiz scanning. This mentorship project will extend Copa's support to cover this new scanning schema using a pre-existing template. Expected Outcome: The mentee will produce the following i. Design doc for Wiz Scanning ii. Wiz Plugin Integration iii. End to End integration tests

TBA
Proposal

Chaos Engineering as a Service

Intermediate
•Varies175h (Medium)

Description: Chaos Mesh is not like Chaos Engineering as a Service now: - Poor observability: the result of chaos experiments are not easy to observe and judge, the users need to check whether the Chaos effects by manual. - Chaosd(for physic node) is too simple: only supports command line operation, does not support task scheduling and life cycle management. - The costs of learning operation and maintenance are high: the maintenance of Chaos Mesh and Chaosd are not unified. - It should be a unified place to manage Chaos experiments for multiple platforms and multiple clusters, and can see the monitoring data of the experiment.

TBA
Proposal

Convert Sample Policies to CEL (2025 Term 3)

Intermediate
•Varies175h (Medium)

Kyverno has introduced new CEL-based policy types in the v1alpha1 API version that provide enhanced expressiveness, better performance, and native Kubernetes integration. These new policy types include ValidatingPolicy, MutatingPolicy, ImageValidatingPolicy, GeneratingPolicy, and DeletingPolicy. The goal of this project is to convert existing sample policies from the traditional Kyverno policy format to the new CEL-based format, ensuring they maintain the same functionality while leveraging the benefits of the new API. Expected Outcome: 1. Convert existing sample policies from traditional Kyverno format to new CEL-based policy types 2. Ensure functional equivalence between old and new policy formats 3. Write tests to validate the conversions and ensure reliability 4. Help users understand how to migrate from traditional policies to CEL-based format

TBA
Proposal

Promote API Version to v1beta1 (2025 Term 3)

Intermediate
•Varies175h (Medium)

Many advance workloads in OpenKruise are widely used in production, however the API version of the workload is still in v1alpha1. The goal is to promote the API version of mostly used and mature workload to v1beta1 and optimize the CRD fields for better clarity. Expected Outcome: 1. API definition of v1beta1 resources and the implementation for conversion webhook to convert v1alpha1 resource to v1beta1 resource 2. Unit and integration tests 3. Documentation for the usage of v1beta1 resource in the OpenKruise website

TBA
Proposal

Create a Workload Analysis Flow Using RISC-V Olympia Performance Model Mentorship Project

Intermediate
•Varies175h (Medium)

Performance research/design of RISC-V CPU designs require workloads for analysis. Workloads can be custom user applications or industry benchmarks such as SPEC, GeekBench, Dhrystone, etc. Using tools like the RVI Olympia Perf CPU Model users can pinpoint bottlenecks in CPU design, the workload, or the compilers/libraries. When the workload is small, running the workload on Olympia is not complex: trace the workload using a functional model and run that trace through Olympia; count cycles. However, if the workload is large, tracing the entire workload is not practical. Workload reduction tools, such as SimPoint, help narrow down the points of interest (POI) as well as reduce the instruction length to calculate estimated performance. The flow using SimPoint: Workload -> SimPoint analysis (using tools like QEMU) -> workload fragments -> trace generation. Each trace can be run in parallel on Olympia to gather the point performance. Post-processing tools will collate the fragments and generate an overall estimate of performance. This internship will: * Establish workloads (research) * Establish a SimPoint flow to reduce the workloads (QEMU or other instruction set simulators) * Generate STF traces using SimPoint data (QEMU or other instruction set simulators) * Create a repository of traces and their metadata, such as compiler info * Tools to run traces on Olympia and generate perf data (python, C++)

TBA
Proposal

Multi-cluster Ambient testing expansion (2025 Term 2)

Intermediate
•Varies175h (Medium)

Istio is a service mesh platform used by thousands of companies to secure and manage their microservices traffic, most often in a single Kubernetes cluster. However, the ability to operate across multiple clusters is an important feature in Istio's traditional Sidecar mode, and work to support it in Istio's Ambient mode is making rapid progress. To call any feature complete, comprehensive testing is needed. Given that multicluster Istio Ambient is a new mode of operating, we will need to both adapt tests for existing features to ensure they work across multiple clusters, as well as identify multi-cluster specific scenarios we want to codify in tests. Expected Outcome: 1. Audit existing ambient integration tests for cases that do not support multi-cluster testing patterns. 2. Refactor those tests, using Istio's testing infrastructure to cover features within a multi-cluster environment. 3. Work with Istio maintainers to identify opportunities for testing new scenarios that exist only for ambient multi-cluster. 4. As documentation is written for https://istio.io, verify that the user instructions (kubectl commands, YAML snippets, etc.) actually work end-to-end. 5. Gain hands-on experience with Istio's codebase, service mesh architectures, and Kubernetes multi-clust......

TBA
Proposal

Convergence of Network and Graph topologies

Intermediate
•Varies175h (Medium)

Use Neo4j's ability to create graph projections, which copy a subgraph to RAM so that algorithms can be efficiently run. This opens the door to leveraging algorithms in the areas of Centrality, Community Detection, Pathfinding, Topological Link Prediction, etc. Bringing to bear advances made in Machine Learning / AI / recommendation systems, fraud detection could really help to derive meaning and comprehension for future tools. Another example is how ML + graph approaches are used to find and determine the optimal molecular structure of atoms such that desired physical properties are targeted. This approach could be applied to the problem of workload sizing and estimation for service mesh operators and would-be adopters.

TBA
Proposal

Upgrade Jaeger-UI to React v19 (2025 Term 2)

Intermediate
•Varies175h (Medium)

Jaeger (https://www.jaegertracing.io/) is an open-source, distributed tracing platform designed to monitor and troubleshoot microservices-based systems. Jaeger-UI is the web UI for Jaeger, built with React (https://react.dev/) . The current version of React used by Jaeger-UI is v18. This project aims to upgrade Jaeger-UI to React v19, in order to stay up to date with the dependencies. Expected Outcome: A working version of Jaeger-UI upgraded to React v19, with all the features and functionality of the current version. This may include a need to upgrade or replace some other dependencies that may not be compatible with the latest React.

TBA
Proposal

Support RK3588 edge nodes (2025 Term 2)

Intermediate
•Varies175h (Medium)

The RK3588 chip, developed by Rockchip, is widely used in edge computing devices due to its balanced computational power, rich interface options, and low power consumption. Supporting RK3588 edge devices is crucial for expanding the KubeEdge ecosystem. However, it has not yet been fully validated whether RK3588-based edge nodes can be seamlessly integrated with KubeEdge. This project aims to establish complete compatibility between RK3588 and KubeEdge. Expected Outcome: 1. Debug and Support KubeEdge EdgeNode running on RK3588 Chip. 2. Successfully deploy edge pods on edge node based on RK3588. 3. Achieve node management and metrics for nodes and pods. 4. Complete hardware compatibility testing and output documentation or a blog.

TBA
Proposal

System Stability Enhancement

Intermediate
•Varies175h (Medium)

Add more UT/E2E to cover more classical scenarios. Conduct complete stress testing and regression testing, Offer test report, give the improvement plan and put it into practice.

TBA
Proposal

Device Anomaly Detection Framework (2025 Term 3)

Intermediate
•Varies175h (Medium)

The current KubeEdge platform represents device states using three statuses: Desired, ObservedDesired, and Reported. The device states displayed on the platform are entirely reliant on the Mapper, which collects and reports data from the device side. However, due to limitations in the Mapper implementation, physical device malfunctions, network delays, and potential network attacks, the device states shown on the platform may not accurately reflect the actual state of the devices. In the KubeEdge platform, if applications depend on device states for decision-making, such inconsistencies in state representation may lead to undesirable outcomes. Therefore, this project aims to design a device state anomaly detection framework for KubeEdge. By exploring the causal relationships among device states, the framework will establish lightweight anomaly detection capabilities and provide a comprehensive toolchain encompassing data collection, model training, real-time anomaly detection, and results visualization. Expected Outcome: 1. A general-purpose device anomaly detection framework that supports user-defined detection algorithms 2. A complete technical design document including model selection, training procedures, and detailed architecture diagrams for both training and online detection components 3. A machine learning model and corresponding anomaly detection algorithm capable of capturing causal relationships among device states, trained and tested using standard frameworks...

TBA
Proposal

Conformance Program (extended)

Intermediate
•Varies175h (Medium)

Ensure that a service mesh is properly configured and that its behavior conforms to official SMI specifications. Advance the definition of conformance tests and the test framework, Meshery (see [design specification](https://docs.google.com/document/d/1HL8Sk7NSLLj-9PRqoHYVIGyU6fZxUQFotrxbmfFtjwc/edit)).

TBA
Proposal

Feature optimizations for RISCV-CTG (Compatibility Test Generator) and RISCV-ISAC (RISCV ISA Coverag Mentorship Project

Intermediate
•Varies175h (Medium)

Introduction RISCV-ISAC: RISC-V ISAC is an ISA coverage extraction tool. Given a set of cover points and an execution trace of a test/application run on a model, ISAC can provide a report indicating in detail which of those cover points were covered by the test/application. ISAC also holds the capability to provide a detailed quality analysis on data propagation occurring within the test/application.RISCV-CTG is the RISC-V based Compatibility Test Generator. This tool is used to generate tests used in the official RISC-V Architectural Test Suite and the RISC-V architectural test framework RISCOF. All tests generated by the CTG are compliant with the official Test Format Spec. The CTG is similar to a constrained test generator capable of generating tests targeting a specific set of constraints. These constraints are supplied to the CTG using the Coverage Group Format (CGF) File. The CGF file contains various cover-points for different instructions. The CTG treats each cover-point as a constraint and employs a solver to identify potential solutions. CTG uses the constraint satisfaction problem (CSPs) solvers offered by the python-constraint package.

TBA
Proposal
Showing 12817 - 12840 of 13453 Projects
533534535536537