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

Map Azure and GCP cloud resources (2025 Term 3)

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)

Cartography (https://github.com/cartography-cncf/cartography) makes maps of the cloud so that security and devops teams can find and fix problems. Think about it like the Maurauder's Map (https://simple.wikipedia.org/wiki/Marauder%27s_Map) from Harry Potter. Cartography has very good AWS coverage, but lacks support for many Azure and GCP resources. With your help, we can fix this! Companies around the world use Cartography to better understand their infra, and you can be a part of this. Most of these modules should be conducive to coding with agents (we have a well-documented AGENTS.md! (https://github.com/cartography-cncf/cartography/blob/master/AGENTS.md), so if you enjoy writing in Python, want to learn about information security/devops, and moving fast, this is the project for you. Expected Outcome: Design and implement graph schemas for missing Azure and AWS objects in Cartography

TBA
Proposal

Convergence of Network and Graph topologies (2024 Term 2)

Intermediate
•Varies175h (Medium)

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. Expected outcome: - Use Neo4j's ability to create graph projections, which copy a subgraph to RAM so that algorithms can be efficiently run.

TBA
Proposal

WasmEdge C++ SDK

Intermediate
•Varies175h (Medium)

Description: WasmEdge provides C SDK as the based library and uses this to implement other languages SDK such as Golang, Rust, Java, and Python(developing). We would like to provide C++ SDK in this task. Expected Outcome: A document to explain the C++ SDK, a test suite cover the implementation details, and the implementation of WasmEdge Basics and VM sections in the C SDK.

TBA
Proposal

Hyperledger Caliper documentation platform update Mentorship Project

Intermediate
•Varies175h (Medium)

The goal of the project is to enhance the accessibility, consistency, and comprehensiveness of the Caliper documentation. This mentorship project aims to transition the current Caliper documentation site to utilize the common documentation template adopted by Hyperledger projects. This standardization effort will ensure a seamless user experience across Hyperledger documentation, facilitating easier navigation and comprehension. Furthermore, the project will focus on content improvement to ensure that the documentation covers all aspects of Hyperledger Caliper comprehensively, including installation, configuration, usage, and troubleshooting, with up-to-date and accurate information. The mentee can gain a wealth of knowledge and skills that are valuable not just for this specific project but for their professional development in technical writing, documentation management, and basic understanding of blockchain technology.

TBA
Proposal

Improving unit test coverage(CAPV)

Intermediate
•Varies175h (Medium)

Description: Cluster API (CAPI) is a Kubernetes sub-project focused on providing declarative APIs and tooling to simplify lifecycle management of Kubernetes clusters. CAPV is the infrastructure provider that extends Cluster API to manage Kubernetes clusters on vSphere. As a mentee, you will start with learning CAPI/CAPV concepts and then, will work on the main project which is to improve unit test coverage.

TBA
Proposal

Support for new types of eBPF programs (2024 Term 1)

Intermediate
•Varies175h (Medium)

Inspektor Gadget is an eBPF tool and systems inspection framework for Kubernetes, containers and Linux hosts. Users can develop gadgets using different kinds of eBPF programs: kprobe, tracepoint, etc. This project will focus on adding support for more kinds of eBPF programs such as uprobes and ensuring the documentation is updated for each of them Expected Outcome: Inspektor Gadget has support for additional eBPF program kinds

TBA
Proposal

Support Podman and OCI Hooks support for unorchestrated environments (2024 Term 3)

Intermediate
•Varies175h (Medium)

Leverage OCI hooks to obtain container start/stop events and container details for KubeArmor, replacing the current UNIX domain socket file method. Integrate Podman support for unorchestrated environments, ensuring policy enforcement and alerts/telemetry validation. Design the implementation to gather necessary container information and verify functionality with Podman as well as Containerd without Unix Socket. Expected Outcome: Work with Podman in rootless mode and Eliminate exposing UNIX domain sockets for other container runtimes

TBA
Proposal

Adopt OCI as the packaging and distribution format for Meshery MeshModels

Intermediate
•Varies175h (Medium)

Meshery MeshModels represent a schema-based description of cloud native infratructure. MeshModels need to be portable between Meshery deployments as well as easily versionable in external repositories. - Expected outcome: - Meshery clients (mesheryctl and Meshery UI) should be able to import/export MeshModels as OCI images. - Meshery clients (mesheryctl and Meshery UI) should be able to push/pull from OCI-compatible registries. - Stretch Goal: OCI image signing; Verify the authenticity of MeshModels using [cosign](https://github.com/sigstore/cosign). - Target registries: Meshery Catalog (https://meshery.io/catalog), Artifact Hub.

TBA
Proposal

Hypereldger - Support Clique for Besu on HL Labs BAF Mentorship Project

Intermediate
•Varies175h (Medium)

Hyperledger Labs Blockchain Automation Framework(BAF) is a tool to deploy different DLT platforms automatically on a given Kubernetes cluster. BAF supports multi-cloud and multi-DLT deployments, and already supports HL Fabric, HL Besu, Quorum, R3 Corda. For HL Besu, currently only IBFT2 Consensus is supported by BAF. With this internship program we want to support the Clique consensus for Besu, so that BAF can be used to deploy and operate a HL Besu network with Clique consensus. This will also include upgrading BAF to support the latest stable Besu version. The mentee will be able to learn: 1) Production grade architecture. 2) evOps in Blockchain Development. 3) Architecture of Besu and BAF. 4) work in true spirit of open-source, communicating with both Besu and BAF community, joining calls and using other community tools. 5) writing documentation, so anyone in the community could use the results of their work. 6) following rules and standards of open-source projects created by Hyperledger. Expected Outcome 1) Documented, ready-to-use Besu Clique consensus on BAF. 2) Documented upgrade of Besu to latest stable on BAF.

TBA
Proposal

Volcano supports DRA integration (2024 Term 1)

Intermediate
•Varies175h (Medium)

DRA (https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/) is a new generation device management mechanism for kubernetes. It introduces a new resource request API `ResourceClaim`, which requires kubelet, kube-controller-manager, scheduler, and third-party device management controllers to cooperate with each other to work. The kube-scheduler has implemented corresponding scheduling capabilities, Volcano also needs to implement the DRA scheduling plug-in to integrate the DRA function. Expected Outcome: - A design document describing how to integrate DRA into volcano. - Implement DRA plugin in volcano.

TBA
Proposal

Enhance Documentation for CEL Policies (2025 Term 3)

Intermediate
•Varies175h (Medium)

Kyverno has evolved significantly with the introduction of new CEL-based policy types in the v1alpha1 API version. The current documentation and website need to be updated to reflect these advancements and position Kyverno appropriately in the policy engine landscape. This project aims to enhance Kyverno's documentation, website content, and overall positioning to showcase the new capabilities while maintaining clear guidance for users transitioning from traditional policies to CEL-based formats. Expected Outcome: 1. Update and enhance Kyverno's website to reflect new CEL- based policy capabilities 2. Ensure comprehensive documentation for all new policy types 3. Update Kyverno's positioning in the policy engine ecosystem 4. Update comparison charts and feature matrices 5. Enhance user experience with better navigation and search functionality 6. Update API reference documentation with new policy types

TBA
Proposal

Add Prometheus Metrics to Control Plane Service (2026 Term 1)

Intermediate
•Varies175h (Medium)

Expose service health, API observability and experiment execution data as prometheus metrics in the chaos manager/litmusportal server Expected Outcome: Public Grafana dashboard for LitmusChaos observability

TBA
Proposal

Property-based tests for tremor-script

Intermediate
•Varies175h (Medium)

Extend property-based testing for tremor script

TBA
Proposal

Kyverno SLSA 3

Intermediate
•Varies175h (Medium)

Implement software supply chain security best practices to achieve SLSA Level 3 compliance (https://slsa.dev/). This includes generation of build provenance data for Kyverno. Kyverno - SLSA.

TBA
Proposal

TrainJob and SparkApplication Resource Interpreters (2025 Term 3)

Intermediate
•Varies175h (Medium)

Develop default resource interpreters for TrainJob and SparkApplication workloads in Karmada. Expected Outcome: The task involves implementing interpreter logic, validating scheduling/propagation, and documenting the process of running these workloads on Karmada. Share the practice and integration details with the Kubeflow and Spark communities.

TBA
Proposal

Integrate Intel Extension for Transformers as a new WASI-NN backend (2024 Term 1)

Intermediate
•Varies175h (Medium)

LLM is a hot topic, there are more and more frameworks to make the execution of LLM faster. WasmEdge already integrated the llama.cpp (https://github.com/ggerganov/llama.cpp) as one of the backend. Running LLM with CPU only is huge for those users who don't have GPU. We would like to integrate Intel Extension for Transformers (https://github.com/intel/intel-extension-for-transformers) as a new WASI-NN backend to provide a faster CPU inference performance. Expected Outcome: A new plugin provides a Intel Extension for Transformers WASI-NN (https://github.com/second-state/wasmedge-wasi-nn) backend, a test suite for validating the plugin, documents and examples for explaining how to use the plugin.

TBA
Proposal

Kubernetes API caching, pagination & search (2025 Term 2)

Intermediate
•Varies175h (Medium)

Headlamp currently fetches Kubernetes API data directly from the frontend, which can lead to performance bottlenecks and unnecessary API load. Introducing a caching layer in the headlamp-server backend will reduce API calls, improve response times, and enable more efficient data handling. This enhancement will also allow for improved pagination—fetching only the data needed for the current view—and enable backend-powered search functionality, reducing the need for the frontend to download large datasets. Expected Outcome: 1. A backend caching layer for Kubernetes API responses, scoped per user context to ensure data isolation and security. 2. A new pagination API that allows the frontend to request only the currently visible page of data. 3. A search API that queries the cached data, enabling fast and efficient search without full data downloads. 4. Documentation and possibly a demo video explaining the architecture and usage of the new caching, pagination, and search features.

TBA
Proposal

Rebuild documentation for multi-version support with Docusaurus (2025 Term 3)

Intermediate
•Varies175h (Medium)

The current documentation of CloudNativePG (a Kubernetes-native Postgres operator) is statically built using mkdocs from Markdown sources, which must live with the rest of the source code as they are part of it. We want to modernise this process and introduce multi-version support, helping users find accurate information for the version they are running in production. This project aims to rebuild the documentation site using Docusaurus (preferred) or an equivalent static site generator to enable multi-version documentation and version selection. Additionally, any initiatives that improve content structure, navigation, searchability, and clarity are welcome, provided they enhance logical flow and maintainability while aligning with CNCF and user expectations. The documentation is hosted on GitHub Pages under the CloudNativePG website domain. Expected Outcome: 1. Incremental set of pull requests (PRs) with: a. Site built with Docusaurus (or equivalent) with version selector working. b. Content restructured for clarity and easier navigation. c. Clean, consistent navigation structure and enhanced search capabilities. d. Staging website capabilities. e. Deployment workflow to GitHub Pages using Dagger and GitHub Actions. 2. A clear contributor guide explaining how maintainers can add or update documentation for each version in the future.

TBA
Proposal

Implement component model's validator (2025 Term 1)

Intermediate
•Varies175h (Medium)

The current validator of component model inside of WasmEdge only check nested module and ensure VM can run the nested modules without problem, but the validations from component model are mostly skipped. Expected Outcome: 1. One should create a workable (merged into upstream) implementation of validator by working on 2. include/validator/validator_component.h 3. lib/validator/validator_component.cpp 4. The visitor pattern are already setup. Recommended Skills: Since component model proposal separate their validation spec, one should able to find requirements from https://github.com/WebAssembly/component-model/tree/main/design/mvp

TBA
Proposal

Documentation assessment and improvements (2024 Term 2)

Intermediate
•Varies175h (Medium)

Open source projects need help with their documentation! The TUF project is a good place to start. We'd welcome help from others to help here and become contributors to other projects / TAGs later in the project period. The mentee will (with minimal guidance from the CNCF team and TUF project) do a CNCF assessment (https://github.com/cncf/techdocs/blob/main/assessments/howto.md) for the TUF documentation. Expected Outcome: Both an improvement of project docs and the development of a new contributor. A mentee will understand how to do technical writing for an open source project.

TBA
Proposal

Add event & alerts infrastructure to the litmus portal

Intermediate
•Varies175h (Medium)

LitmusChaos is a Kubernetes native chaos engineering framework that helps SREs & developers find weaknesses in their deployments, with the chaos intent being defined via custom resources. The Litmus portal is a dashboard focused on simplifying the chaos-engineering experience for users and allows the execution of complex "chaos workflows" that comprise one or more chaos experiments. This portal dashboard needs to be improved to hold more observability information, primarily in the form of an event log & alerts to help users gather important information about the state of the chaos experiments & cluster in general.

TBA
Proposal

Supply Chain Security with SLSA L3 and OpenSSF Scorecard Hardening (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>KubeArmor is a runtime security engine that enforces zero-trust policies at the kernel level. As a security-critical project in the CNCF ecosystem, it must hold its own supply chain to the highest standards. This project focuses on two tightly related goals. First, achieving SLSA Level 3 compliance by auditing KubeArmor's build and release pipeline against the full SLSA L3 specification — covering hermetic builds, non-falsifiable provenance generation via SLSA GitHub Actions, and signed release attestations using cosign. KubeArmor already signs container images; this project closes the remaining gaps by following a strategy similar to KubeEdge's documented SLSA L3 journey. Second, improving KubeArmor's OpenSSF Scorecard rating by systematically addressing low-scoring checks - including Signed-Releases, Fuzzing (OSS-Fuzz integration), SAST (CodeQL), Pinned-Dependencies, and CII Best Practices. Also integrating the Scorecard GitHub Action into CI for continuous score tracking. The pre-task for mentee candidates will be submitting a pull request that enables and verifies the Signed-Releases check on KubeArmor's OpenSSF Scorecard, establishing a clear baseline before the full term begins.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Full SLSA Level 3 compliance for KubeArmor releases, with SLSA provenance attestations generated and published for each release artifact</p><p>&nbsp;- Signed release artifacts (binaries, container images, SBOMs) verified end-to-end using cosign and SLSA verifier</p><p>&nbsp;- Measurable improvement in KubeArmor's OpenSSF Scorecard aggregate score, with targeted checks resolved: Signed-Releases, Fuzzing, SAST (CodeQL integration), and Pinned-Dependencies</p><p>&nbsp;- OpenSSF Scorecard GitHub Action integrated into KubeArmor's CI pipeline for automated, ongoing score tracking</p><p>&nbsp;- A gap analysis document and follow-up GitHub issues capturing any remaining SLSA or Scorecard items for future contributors</p><p>&nbsp;- Documentation covering the supply chain security posture: how to verify release provenance, how to reproduce builds, and how Scorecard checks are enforced</p><p><br></p>

TBA
Proposal

An Extended RISC-V Microcontroller Core

Intermediate
•Varies175h (Medium)

"Overview: The UETRV PicoCore project aims to enhance the capabilities of the existing UETRV_Pcore RISC-V core, making it a versatile and feature-rich open-source microcontroller. The core is RV32IMA Linux-compatible and Privilege Architecture 1.10 compliant, and we envision integrating essential extensions such as bitmanip, floating point, debug, trace, and GPIO peripherals. This initiative aligns with the broader goal of providing a comprehensive RISC-V MCU solution that is accessible to the open-source community. Tasks: Bitmanip Extension Integration: The Bitmanip extension offers advanced bitwise manipulation instructions. The task involves integrating this extension into the existing UETRV_Pcore, optimizing its usage, and ensuring compatibility with existing codebases. Floating Point Extension Integration: Incorporating the Floating Point extension will enable hardware-accelerated floating-point computations. This task involves integrating the extension into the core, optimizing performance, and ensuring compliance with the RISC-V standard. Debug, Trace, and GPIO Peripherals: Enhancing the microcontroller's capabilities, this task involves integrating debug and trace functionalities for improved development and debugging. Additionally, GPIO peripherals will be integrated to facilitate easy interfacing with external devices.

TBA
Proposal

Enriching AWS chaos

Intermediate
•Varies175h (Medium)

We have already made a technical previewing implementation for AWS Chaos, it could inject some simple chaos now, such as stop/restart the EC2. And we want to make it more stable and structured. And there is another direction of AWS chaos: AWS service failure. It might be useful for testing infrastructure automation tools. Basically, there are two things that we want to do: - enriching e2e test cases using localstack - more chaos by simulating AWS service failure by hijacking awscli request to a modified localstack.

TBA
Proposal
Showing 553 - 576 of 1243 Projects
2223242526