Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
<p>The RISC-V Extensions Landscape is an open-source, interactive web tool that serves as a single searchable reference for the entire RISC-V Instruction Set Architecture ecosystem. It visualizes all ratified, draft, and discontinued extensions, displays per-instruction 32-bit encoding diagrams with match/mask values, and supports filtering by RISC-V profiles (RVA20, RVA22, RVA23, RVB23). The project is live at https://rpsene.github.io/riscv-extensions-landscape/ and built with React, Tailwind CSS, and Webpack.</p><p><br></p><p>The core challenge is that only 83 of 220 cataloged extensions (38%) have their instruction details fully mapped. The remaining 137 extensions exist in the catalog but lack instruction encodings, leaving significant gaps in supervisor-level extensions (trap, interrupt, memory), vector subsets, and vector cryptography bundles. Additionally, 104 extension tags from the upstream riscv-opcodes project remain unlinked due to naming mismatches between the source data and the catalog, preventing automated synchronization.</p><p><br></p><p>The mentee will work on three main tasks: (1) reconcile the 104 mismatched extension tags from riscv-opcodes with the catalog's naming conventions, enabling the sync script to automatically populate instruction data; (2) research and map instructions for the remaining extensions, particularly supervisor-level extensions that define CSR behaviors and vector subset extensions that represent subsets of the V extension; and (3) improve the sync tooling to detect gaps and generate coverage reports automatically. The mentee will gain hands-on experience with the RISC-V ISA, open-source data engineering, and React-based visualization tools.</p><p> </p>
In today's data-driven world, leveraging legacy data can be a game-changer for businesses. By integrating AI with Retrieval-Augmented Generation (RAG), organizations can unlock the hidden potential of their historical data. RAG combines the power of large language models with a retrieval mechanism that fetches relevant information from vast datasets. This approach not only enhances the accuracy and relevance of AI-generated responses but also ensures that valuable insights from legacy data are utilized effectively. Whether it's improving customer service, optimizing operations, or driving innovation, RAG empowers businesses to transform their legacy data into a rich source of actionable intelligence, paving the way for a more informed and strategic future. Deliverables: Detailed research and conceptual framework document (whitepaper) to implement AI that uses mainframe data.
We are seeking enthusiastic applicants who want to elevate and add to the suite of hands-on labs offered in the COBOL Programming Course. The ideal candidate will have reviewed the COBOL Programming Course content and have some initial recommendations/ideas on labs to add to the course. The COBOL Programming Course uniquely offers an opportunity for learners to gain hands-on experience with mainframe and COBOL development. To further this differentiation, we need to add more comprehensive labs to the course. Deliverables: We would like to also add at least 5 hands-on labs as well to reinforce what is learned in the course. All hands-on labs in the COBOL Programming Course will be reviewed and improved if opportunities are identified.
The executable behavior of the RISC-V specification is encoded in UDB using a language called ISA Description Language (IDL). IDL is syntactically similar to C/C++/Verilog, but is both strongly and statically typed to eliminate ambiguity. This mentorship opportunity will involve the development and maintenance of IDL code in the database. Tasks could include writing a RISC-V extension in IDL (for example, the Vector extension), testing existing IDL using compliance tests, and fixing IDL bugs. Familiarity with a hardware description language like Verilog, design verification, and computer architecture are desirable.
<p>*APPLICATION ONLY OPEN TO STUDENTS IN INDIA*</p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>SONiC is a database-centric NOS: much of the control-plane and operational state is available in Redis, and telemetry can poll/subscribe to DB data. There are a variety of interesting analytics and telemetry data that can be extracted from this DB, many by leveraging Redis capabilities. However, directly adding heavy analytics (e.g., long-running server-side scripts) to the primary Redis risks impacting normal SONiC applications. Redis Lua scripts execute atomically but block the server for the full runtime of the script. This project proposes a low-risk pattern: create a Redis replica (master → replica) that maintains a synchronized copy of selected SONiC databases, and run the analytics plane on the replica. </p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><ul><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Design and prototype a “shadow analytics plane” using Redis replication (master → replica) so normal SONiC apps continue to use the primary Redis instance unchanged. Design and implement cold boot, Warmboot and fast-boot.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Implement use-cases, some examples”</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Incident Forensics (A): Build a flight-recorder capability on the replica that can reconstruct recent sequences of “interesting” changes (timeline) and provide a compact incident summary.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Alert Storm Reduction (B): Build novelty detection and heavy-hitter summarization on the replica to suppress repeated alerts and highlight top recurring signatures.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Provide operational documentation: how to deploy, how to tune retention/limits, and how to validate that primary-path performance is not affected.</span></li></ul><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Strong Linux fundamentals; comfortable working in containerized environments.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Python and/or Go proficiency (for collectors, processors, and CLI tooling).</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Basic understanding of Redis concepts (pub/sub, streams, replication) and willingness to learn SONiC DB schemas.</span></li><li><span style="color: rgb(0, 0, 0); background-color: transparent;">Interest in reliability engineering / observability / operational tooling.</span></li></ul><p><br></p>
<p>Hyperledger Identus provides mature backend services (Cloud Agent, Mediator) and Edge Agent SDKs (TypeScript, Kotlin Multiplatform, Swift) for building Self-Sovereign Identity (SSI) solutions.</p><p><br></p><p>This mentorship project will deliver a lightweight, unified agent interface — primarily a web-based reference dashboard — that supports:</p><ul><li>Offline-first / non-custodial mode — powered entirely by the TypeScript Edge Agent SDK running in the browser, with CIP-30 Cardano wallet integration (via MeshSDK) for PRISM DID operations.</li><li>Connected / custodial mode — optional connection to an existing Cloud Agent instance via a configurable API endpoint.</li></ul><p>Core architectural principles</p><ul><li>Offline-first by default — If no <code style="background-color: rgba(129, 139, 152, 0.12);">CLOUD_AGENT_API_ENDPOINT</code> is provided, the application runs fully in the browser with no backend dependencies.</li><li>Maximal reusability — Core SSI logic is built as pure TypeScript modules / utilities that can be reused in other projects (web, React Native,, custom dApps, etc.).</li><li>Minimal vendor lock-in — No UI component kits (e.g., no shadcn/ui); use plain Tailwind CSS + simple, custom, portable components.</li><li>Stable & compatible stack — Target React 18 (latest stable non-experimental version) to maximize future compatibility with projects.</li><li>Modular structure — Separate concerns: pure SSI logic → service adapters (Edge vs Cloud) → presentation layer.</li></ul><h3>Learning Objectives</h3><ul><li>Deep understanding of SSI concepts: Decentralized Identifiers (DIDs – especially PRISM method), Verifiable Credentials (JWT, SD-JWT, AnonCreds), schemas, revocation, DIDComm messaging, trust frameworks, issuer/holder/verifier roles</li><li>Hands-on experience with the Hyperledger Identus ecosystem: Cloud Agent REST APIs, TypeScript Edge Agent SDK, Mediator coordination, PRISM DID resolution & publishing to Cardano, Verifiable Data Registry</li><li>Building reusable, framework-agnostic TypeScript code for SSI workflows</li><li>Implementing a unified UI system for both the Cloud Agent and the Edge Agent (offline first)</li><li>Practice open-source development workflows, including code review, documentation, community engagement, and incremental delivery</li></ul><p><br></p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/77" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/77</a></p>
<p>The Web3j library is an essential tool for Java and JVM-based developers looking to integrate with the Ethereum blockchain. It provides seamless Ethereum client communication, enabling developers to interact with smart contracts and blockchain networks. However, maintaining and improving Web3j while ensuring seamless adoption of the latest Ethereum Improvement Proposals (EIPs) remains a challenge for maintainers due to the lack of time and contributors.</p><p><br></p><p>This project aims to enhance the core Web3j by improving and continue to keep up to date its component libraries, focusing on reducing existing issues and integrating the missing EIPs. By improving the additional Web3j libraries, we aim to streamline development workflows, enhance testability, and create a more robust framework that simplifies Ethereum development for Java and JVM-based projects. The updates will address known gaps in the libraries, ensuring compatibility with the latest Ethereum standards while improving documentation, developer experience, and maintainability.</p><p><br></p><p>A similar mentorship project took place during the last mentorship program and resulted in significant code contributions, documentation and blog posts.</p><p><br></p><p>The initiative will introduce structural improvements, new features and documentation for better integration, and testing, making Web3j a more sustainable and adaptable web3 development tool project.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Gain hands-on experience contributing to an open-source blockchain library, improving their understanding of Ethereum integration in JVM applications.</li><li>Develop expertise in Java and its application in blockchain smart contract development.</li><li>Enhance their skills in software libraries architecture, Ethereum blockchain and Solidity Smart Contracts development practices.</li><li>Collaborate with an open-source community, learning best practices for issue tracking, code reviews, and pull request management.</li><li>Develop expertise in complex library release process and code management.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/60" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/60</a></p>
<p>With the move of the Hedera's code base to Hiero, the project expanded significantly in scope. The SDKs that are currently available are all coming with the limited scope to Hedera and the Hedera network. Additionally, some of the SDKs are not created in the best possible way for the underlying programming language. Therefore, SDK usage is from time to time hard to understand and developers often run into issues. With all the changes to Hiero over the last year, including the modularization of the consensus node and the support for custom services and transactions, the architecture and public API of the SDKs is outdated in several ways. While we want to provide a great developer experience for our users, the current SDKs are not suitable for the future.</p><p>Based on all these factors, we started to invest in prototyping a possible new architecture and API for the future of our SDKs. That work is currently named "SKD V3" and happens in the <a href="https://github.com/hiero-ledger/sdk-collaboration-hub" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">SDK collaboration hub of Hiero</a>. We currently define language agnostic APIs and language best practices for architecture and APIs of the future SDKs. Regarding general language agnostic API design, our <a href="https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/api-guideline.md" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">API guideline</a> is a good starting point. Based on that guideline, we created a <a href="https://github.com/hiero-ledger/sdk-collaboration-hub/tree/main/v3-sandbox/prototype-api" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">draft of the new SDK architecture and APIs</a>.</p><p>As a next step we need to create PoCs for the new SDK architecture and APIs in multiple languages. The main goal of this mentorship program project is to:</p><ul><li>Create PoCs for the new SDK architecture and APIs in multiple languages.</li><li>Create a roadmap for the new SDK architecture and APIs.</li><li>Contribute to our guidelines and documentation to make the new SDK architecture and APIs more accessible to developers.</li><li>Check how AI (like Claude code or GitHub Co-Pilot) can be used as a helpful tool when working on SDK code with all our guidelines and documentation in context.</li></ul><h3>Learning Objectives</h3><ul><li>Understand Hiero and how Hiero based networks work.</li><li>Understand the Communication between a Hiero network (a consensus node and a mirror node) and a client.</li><li>Understand the current SDKs of Hiero and how they work.</li><li>Learn how to create future proof and non breaking APIs.</li><li>Learn how to use language features like generics and type inference to create the best possible SDKs.</li></ul><h3>Expected Outcome and Deliverables</h3><p>The successful completion of this project will result in at least 3 SDK V3 PoCs in multiple languages. Next to that we hope that contributions can be done to the general API guidelines and specifications.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/71" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/71</a></p>
<p>Hyperledger Fabric-X introduces a new architecture for Fabric, with decomposed services for ordering, endorsement, validation, and committing, but its current developer workflow is still centered around dedicated deployment scripts and Ansible-based setup.</p><p>Fablo, on the other hand, is widely used to start Hyperledger Fabric networks quickly from a single configuration file for local development, CI, and experimentation.</p><p>This project will explore and implement the best path to support a simple local Fabric-X network through the Fablo experience. We will evaluate architectural options such as a new engine, a separate repo, or an extension/wrapper approach, then build a minimal but practical MVP that can generate configuration, bootstrap the required components, and start/stop a working local Fabric-X network. The goal is to reduce setup friction for contributors and users, and provide a repeatable developer workflow, examples, and documentation that make Fabric-X easier to try, demo, and extend.</p><h3>Learning Objectives</h3><ul><li>Understand the architecture and deployment model of Hyperledger Fabric-X, including how it differs from classic Hyperledger Fabric.</li><li>Learn how to design contributor-facing tooling for distributed systems with evolving architecture.</li><li>Gain experience in open source development across CLI/tooling, configuration generation, testing, and documentation.</li><li>Develop practical skills in Docker-based environments, and debugging multi-component systems.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>A design proposal describing the recommended integration path between Fablo and Fabric-X (for example: separate repo, pluggable engine, or wrapper-based approach).</li><li>An MVP implementation that can bootstrap a simple local Fabric-X network and manage its lifecycle.</li><li>Example configuration(s) and sample workflow for running Fabric-X through the proposed Fablo-based experience.</li><li>Automated tests and/or validation scripts covering the supported MVP scenario.</li><li>Contributor and user documentation explaining setup, architecture decisions, and next steps.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/83" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/83</a></p>
LF Research publishes actionable and decision-useful insights into open source software, hardware, standards, and data based on empirical research methodologies. Through leveraging community networks, project databases, surveys, and qualitative findings, and through its commitment to best practices in primary research, Linux Foundation Research is the definitive home for data-driven insights into open source for the benefit of governments, enterprises, and society at large.
The Internet Printing Protocol (IPP) does not only support printing, but also scanning, as there are many printers which also have a scanner (multi-function (MF) devices). Both CUPS and the developer tool ippserver emulate IPP network printers but not IPP scanners and so they cannot serve as a server to share a local scanner. This task is about adding the scan server functionality. If you have a scanner connected locally (and it scans via SANE), share it as an IPP scanner, advertising itself and accepting jobs using the IPP driverless scanning standard. In contrary to SANE-based network scanning clients with any operating system, also phones or IoT devices can scan on your shared scanner. Also old hardware can be recycled to a modern MF device. This server software will be a so-called Scanner Application, a sample implementation of the future form of scanner drivers, easily packageable in sandboxed, distribution-independent package formats like Snap.
WasmEdge can load the WASM binary and instantiate into WASM module instances for execution. In an use case, we need to serialize the loaded WASM data structure back into the encoded WASM binary, or deserialize the serialized one into the WASM data structure in WasmEdge. With the serializing mechanism, WasmEdge can control the WASM binary wisely such as caching or snapshotting.
Fully Open Source UI Tools to create web apps. n nCMS and Dashboards built on top of .Net Core, Angular.JS and Bootstrap. n nCreating your web from scratch with the dedicated experience development team can be very expensive. Using our solutions you don't have to worry about tech.
<p>Hyperledger Cello is an enterprise-grade Blockchain-as-a-Service (BaaS) platform that provides a comprehensive REST API for managing the full lifecycle of Hyperledger Fabric networks (Network, Node, Channel, Chaincode). However, all current operations require users to interact manually through the Dashboard, which presents a steep learning curve for newcomers.</p><p><br></p><p>This project aims to implement an AI-powered operation agent with chatbot interface for Hyperledger Cello. It consists of two components:</p><p><br></p><ol><li>AI Agent Backend: A Python service that wraps Cello's existing REST APIs into LLM. It accepts natural language requests, invokes Cello operations, and returns structured responses. It also provides AI-assisted fault log summarization for common Fabric failures.</li><li>Chatbot UI — A chatbot interface integrated into Cello's existing Dashboard (React), allowing users to interact with the AI agent.</li></ol><p><br></p><p>The combined system enables a natural language-driven operational workflow:</p><p><br></p><p>User (chat message) → Chatbot UI → AI Agent → Cello REST API → Fabric Infrastructure</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Open Source Collaboration: Familiarity with Hyperledger Cello workflow, code review standards, and CI pipeline.</li><li>Full-Stack Engineering: Experience building a production-integrated feature spanning a Python backend and a React frontend.</li><li>Applied AI Engineering: Proficiency in LLM Tool Calling integration, streaming response handling, and prompt engineering.</li><li>Blockchain Infrastructure: Hands-on understanding of Hyperledger Fabric network topology, node types, and Chaincode lifecycle.</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>Deliverable: AI Agent Backend</li><li>Acceptance Criteria: Python service exposing a chat API endpoint; supports natural language execution of core Cello operations (list/create networks, manage nodes, query channels and chaincodes)</li></ul><p><br></p><ul><li>Deliverable: Chatbot UI (Dashboard)</li><li>Acceptance Criteria: Chat panel integrated into Cello's existing React Dashboard; supports streaming responses; maintains multi-turn conversation context</li></ul><p><br></p><ul><li>Deliverable: Documentation</li><li>Acceptance Criteria: Setup guide for the AI agent</li></ul>
Linux kernel is the largest open source project with 2+ million lines of code and 10,000 developers across the globe. It is a challenge to understand how the community works, how to get started learning the code base, and take steps to become a contributor. This project will help the applicants help navigating the code base, community, and guide them in choosing the areas of the kernel, finding kernel bugs to focus on, and developing a solution working with the experts in the community. After the end of the project, the applicant will have a much deeper knowledge of many different areas of the Linux kernel and get their patches accepted into the kernel.
Move2Kube is a command-line tool for automating creation of Infrastructure as code (IaC) artifacts. The tool has a powerful plugin based transformer architecture where developers can write their own custom transformer plugins to fulfil their re-platforming needs. However, concepts like path mappings etc could be simplified for better adoption. Example - writing a Move2Kube custom transformer needs developers to understand various concepts such as path mappings etc, can we reduce this learning overhead by simplifying the Move2Kube architecture? Expected Outcome: - Come up with a simplified alternative design for plugin architecture for M2K - Migrate existing components to support the new design with backward compatibility (good to have).
Thanos uses gRPC for the majority of network communication. It performs fanouts and sharding of different queries to multiple nodes in a distributed system. Unfortunately, due to the nature of the gRPC, a conventional TCP-based load balancer (e.g. K8s Service) is not enough to distribute requests equally to multiple replicas of the same stateless node. As a result, there is a need to figure out the pragmatic way for Thanos users to load balance requests to multiple backends either by gRPC client load balancing or by guides and integration with popular load balancing proxies like nginx, caddy or envoy. Upstream Issue (URL): - https://github.com/thanos-io/thanos/issues/3016 - https://github.com/thanos-io/thanos/issues/1083
Latency Tolerance Reporting is used to help manage ASPM (Active State Power Management). Some of the LTR values are platform-dependent and must be learned from platform firmware. Linux currently does not ask firmware for this information. I don't know exactly how this information needs to be incorporated into the ASPM support, but I think it's something we should figure out. See the PCI Firmware Spec, r3.2, sec 4.6.6.
Cilium would like to have use case pages built out on its website to make it easy for people to find the information and relevant content to the problems they are trying to solve with Cilium. Expected Outcome: The mentee will read through relevant docs, blogs, case studies, user stories, and labs to understand the use cases which will drive the content for each of the pages being built. The finished product will be a new use cases section on the Cilium website.
<p>Artificial Intelligence (AI) presents an opportunity to accelerate and de‑risk mainframe data modernization by automating the most complex and labor‑intensive aspects of understanding, extracting, and rebuilding legacy workloads.</p><p>This project will deliver a comprehensive framework that guides organizations through understanding legacy mainframe data structures, mapping those datasets to modern cloud‑based platforms, and applying effective methods for data transfer, quality checks, and validation. As part of this effort, the participant will also develop a demonstration application that showcases the practical implementation of key elements of the framework, illustrating how each component works together to support a successful modernization journey.</p><p><br></p><p>Deliverables:</p><p>A technical framework</p><p>A whitepaper to be published under the modernization working group banner.</p><p><br></p><p><strong>Applications closing date: 25-Apr-2026</strong></p><p><br></p><p><strong>Mentee confirmation: 10-May-2026</strong></p>
<p>Advance thought leadership around what it means to modernize the mainframe. Our mentorship program offers you the chance to research, analyse, and document strategies for modernization of mainframes and the applications workloads that run on top of it. You'll work closely with a mentor and connect with top industry professionals.</p><p><br></p><p>Deliverables: A whitepaper to be published under the modernization working group banner.</p><p><br></p><p><strong>Applications closing date: 25-Apr-2026</strong></p><p><br></p><p><strong>Mentee confirmation: 10-May-2026</strong></p>
<p>Control-flow integrity (CFI) is a fundamental security mechanism that prevents attackers from hijacking a program's execution flow. By exploiting memory vulnerabilities, such as stack-smashing or use-after-free bugs, malicious attackers can corrupt pointers or overwrite return addresses, thereby silently redirecting execution to arbitrary malicious code. RISC-V has recently ratified two ISA extensions to enforce CFI at the hardware level through two complementary primitives. The shadow stack maintains a separate, hardware-protected copy of return addresses, preventing a corrupted call stack from redirecting returns to malicious code. Landing pads require that all valid indirect jumps must land at an explicitly marked location with a special instruction, preventing attackers from redirecting execution to unintended locations.</p><p><br></p><p>In collaboration between the Barcelona Supercomputing Center (BSC) and the SUSHI research team (Inria Rennes), this project aims to implement both CFI extensions on Sargantana, an open-source, Linux-capable, RISC-V core. The mentees will begin by studying the RISC-V CFI specification and the Sargantana microarchitecture, and will then produce an architectural plan of the required pipeline modifications. The mentee will then implement the shadow stack mechanism, including hardware enforcement of shadow stack semantics and access-protection logic. This will be followed by landing pad support, which will involve pipeline enhancements to validate indirect branch targets at commit time. Finally, the mentee will use the Sargantana emulation infrastructure to ensure functional correctness of the implemented extensions and to study the hardware overhead they impose.</p>
Currently, Terraform Controller supports inline HCL, but community users normally already stored Terraform HCLs remotely (in Git repo or ConfigMap). Terraform Controller should support remote HCLs.
As a golang library integrate OPA into Meshery Server, enabling users to define policies to dictate the manner in which their cloud native infrastructure is to both run and be configured. Design an extensible policy framework in which rules may be augmented and dynamically supplied at runtime.