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><span style="color: rgb(67, 67, 67);">The RISC-V ecosystem currently lacks a streamlined and reproducible workflow for executing Architecture Compliance Tests (ACT) on real hardware platforms such as the Vision five 2, Milk-V Jupiter board. While ACT frameworks are widely used in simulation environments, running these tests directly on hardware involves complex boot flows (SPL, OpenSBI, U-Boot), firmware configuration, and low-level debugging. This creates a barrier for developers and new contributors who aim to validate RISC-V implementations in practical environments.</span></p><p><br></p><p><span style="color: rgb(67, 67, 67);">This mentorship project aims to bridge that gap by developing a minimal and reusable M-mode firmware runner capable of loading and executing ACT ELF binaries on the hardware platform. The mentee will explore the board’s boot architecture, implement ELF loading mechanisms, handle trap/debug scenarios (e.g., illegal instructions, FPU enablement), and establish communication via UART for result reporting. A key focus will be enabling reliable PASS/FAIL detection using the standard tohost interface and ensuring execution correctness through memory and cache coherency handling.</span></p><p><br></p><p><span style="color: rgb(67, 67, 67);">The project will follow a structured implementation path: initial environment setup and ACT framework familiarization, followed by firmware development and debugging, and finally automation and documentation. The mentee will create scripts to run multiple ACT tests, capture logs, and generate validation reports. All deliverables will be open-sourced, including firmware, tooling, and step-by-step documentation, contributing a practical reference workflow for RISC-V hardware validation and supporting broader community adoption as per Company Policy.</span></p>
<p>OpenEverest is an open-source cloud-native database platform that helps developers deploy and manage PostgreSQL, MySQL, MongoDB, and other databases on Kubernetes. In V2 it uses a plugin architecture where database providers define their UI through declarative YAML schemas (UISchema in Provider CRD). Currently, plugin developers have no integrated tool for developing and testing these schemas — the only way to see the rendered result is to deploy a full Provider CRD into a running Kubernetes cluster, making the development cycle slow and error-prone. This project aims to build a Plugin Developer Playground — a page inside OpenEverest where plugin developers can write UISchema YAML, see the rendered form in real time, validate the schema structure, inspect the post-processed API payload, and save/share schemas, all without deploying to a cluster. The mentee must solve the CSP compatibility problem by either choosing a CSP-compliant code editor or proposing an isolation architecture (e.g., sandboxed iframe) that keeps the main application's strict security posture intact.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>Split-pane YAML editor with syntax highlighting and live form preview using the existing `UIGenerator` component</li><li>Real-time schema validation: YAML parsing errors and structural validation against the `TopologyUISchemas` type, with inline error markers in the editor</li><li>Live form rendering with stepper navigation through schema sections and topology switching</li><li>Dynamic field support: existing API provider fields load real data from the running OpenEverest instance; new/unknown provider types can be mocked</li><li>Output panel displaying the JSON payload after form data post-processing</li><li>CSP-compliant solution</li><li>Unit tests for core logic (schema validation, persistence, mock data injection) and component tests for key panels</li><li>Plugin developer guide for using the playground and the UISchema format</li></ul>
<p>[Headlamp](https://headlamp.dev) is an open-source, extensible Kubernetes web UI offering easy cluster management, multi-cluster support, RBAC, and a plugin system for adding custom functionality. Users who work with Kmesh today have to switch back and forth between Headlamp (for general Kubernetes resource management) and CLI tools / `kubectl` (for Kmesh-specific inspection), which creates a fragmented workflow and a poor user experience. There is currently no simple visual way to view Kmesh resources, inspect waypoints and related components, understand overall mesh status, or troubleshoot issues quickly from within an interface users already use. This project proposes building a Headlamp plugin for Kmesh that brings Kmesh resources directly into the Headlamp UI, providing lightweight visibility of Kmesh resources alongside other Kubernetes resources. The full-featured Kmesh dashboard remains the place for advanced operations; the Headlamp plugin focuses on reducing context switching and improving ease of use for day-to-day workflows.</p><p><br></p><p><br></p><p>Expected Outcome:</p><p><br></p><p> - A Headlamp plugin (TypeScript/React) that registers Kmesh CRDs and surfaces them as first-class resources in the Headlamp UI.</p><p><br></p><p> - List and detail views for core Kmesh resources (e.g., waypoints and eBPF map)</p><p><br></p><p> - Visual indicators of mesh status: per-resource health, readiness, and recent Events; cluster-level summary of Kmesh components.</p><p><br></p><p> - Inspection helpers: pretty-printed YAML, related-pod views, and quick links to associated workloads/services.</p><p><br></p><p> - Documentation (README, screenshots, install guide) and a published plugin (Helm/manifest or Headlamp plugin registry entry).</p><p><br></p><p> - Unit/component tests for the plugin and an end-to-end smoke test against a kind/minikube cluster running Kmesh.</p>
<p><span style="background-color: transparent; color: rgb(0, 0, 0);">The purpose of this project is to enhance the (</span><a href="https://openssf.org/projects/repository-service-for-tuf/" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(17, 85, 204);">Repository Service for TUF RSTUF</a><span style="background-color: transparent; color: rgb(0, 0, 0);">) implementation by tackling critical areas that would significantly improve its functionality, scalability, and ease of adoption. RSTUF is designed to manage content distribution efficiently using the TUF (</span><a href="https://theupdateframework.io/" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(17, 85, 204);">The Update Framework</a><span style="background-color: transparent; color: rgb(0, 0, 0);">), but it currently has areas where improvements in delegation flexibility, performance, testing, and documentation are needed. This project will allow RSTUF to handle larger and more complex scenarios, while providing an improved experience for both developers and adopters.</span></p><p><br></p><h2><strong style="background-color: transparent; color: rgb(0, 0, 0);">Goal</strong></h2><p><br></p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Add support for more signing schemes for hash-bin delegations under custom delegations: </strong><span style="background-color: rgb(255, 255, 255); color: rgb(0, 0, 0);">Enhance the flexibility of RSTUF’s delegation model to allow for more fine-grained delegation control</span></p><p><strong>TUF visualizer</strong>: Integration of a community-developed visualizer into RSTUF's deployment</p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Improve documentation to facilitate easier adoption</strong><span style="background-color: transparent; color: rgb(0, 0, 0);">: Enhance the user-facing documentation to make it clearer, more comprehensive, and more accessible for new adopters, thus accelerating the onboarding process.</span></p>
<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> - Full SLSA Level 3 compliance for KubeArmor releases, with SLSA provenance attestations generated and published for each release artifact</p><p> - Signed release artifacts (binaries, container images, SBOMs) verified end-to-end using cosign and SLSA verifier</p><p> - Measurable improvement in KubeArmor's OpenSSF Scorecard aggregate score, with targeted checks resolved: Signed-Releases, Fuzzing, SAST (CodeQL integration), and Pinned-Dependencies</p><p> - OpenSSF Scorecard GitHub Action integrated into KubeArmor's CI pipeline for automated, ongoing score tracking</p><p> - A gap analysis document and follow-up GitHub issues capturing any remaining SLSA or Scorecard items for future contributors</p><p> - 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>
<p>Hyperledger Solang is a Solidity compiler to multiple non-EVM targets, including Stellar's Soroban. The Soroban VM is inherently different than the EVM. Also, How Solang translates Solidity to Soroban's WASM is different from the Rust SDK: A different storage layout, different encoding/decoding mechanisms and different optimizer passes as well.</p><p><br></p><p>The main smart contracts SDK for Soroban is <a href="https://github.com/stellar/rs-soroban-sdk" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">the Rust soroban SDK</a>. The purpose of this mentorship is to do an in-depth evaluation of Solang's soroban contracts runtime cost and behavior against the main Rust SDK. This evaluation is critical to Solang's health: We need a reproducible way to validate the design choices of how Solang handles storage operations and encoding/decoding on Soroban.</p><p><br></p><p>The mentorship will be in 3 stages:</p><ol><li>Getting familiar with Solang's code base. This could be done by implementing a Soroban specific feature in Solidity. This task will touch all stages of the compiler, thus enabling the mentee to get familiar with the code base as well as concepts around the Soroban VM and Solidity.</li><li>Implement a differential testing tool for the currently supported Soroban Solidity contracts. The tool should take an input a Solidity contract and a Rust contract, and should provide:</li><li class="ql-indent-1">Runtime cost comparisons, ideally by deploying to Solang's mock Soroban VM.</li><li class="ql-indent-1">Behavioral comparison.</li><li class="ql-indent-1">An interpretation of <span style="color: rgb(31, 35, 40);">the runtime cost for each contract, i.e number of Soroban host function calls, guest memory used, etc...</span></li><li>Publish a list of recommendations that Solang (or the Rust SDK) should improve. Recommendations should be backed up with evidence from the tool defined at stage 2</li></ol><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/74" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/74</a></p>
<p>Design and implement a secure, auditable platform that enforces pre-execution authority for delegated actions initiated by humans, AI agents, and services. The platform will provide a single gateway for policy-driven request routing, a secret vault for API keys and credentials, and a delegation graph model to represent and evaluate long/deep delegation chains with real-time revocation and immutable proofs recorded to a ledger. Initial work will implement core components (gateway, policy evaluator, delegation graph, secret vault integration, immutable audit records) and end-to-end flows for common delegation scenarios. Later work will extend policy negotiation between agents, security reasoning modules, and audit reporting that derives intent and policy-improvement recommendations. The goal is a practical mentorship project that teaches secure authority delegation, DLT-backed auditability, and interoperable identity and credential patterns.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Understand and implement delegation models and graph-based authority evaluation.</li><li>Build a policy-driven gateway that enforces pre-execution checks and real-time revocation.</li><li>Integrate secure secret storage and key management for service/API credentials.</li><li>Record tamper-evident audit trails on an immutable ledger and derive actionable audit reports.</li><li>Apply decentralized identity / verifiable-credential concepts to authorize principals (human, agent, service).</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>Working prototype of a single gateway enforcing policy-checked executions with revocation support.</li><li>Delegation Graph module with algorithms for evaluation and path resolution.</li><li>Secret Vault integration (API for storing/retrieving encrypted keys) and sample connectors.</li><li>Immutable audit-log storage adapter (ledger integration) and a basic audit-report generator.</li><li>Documentation: architecture diagram, developer guide, onboarding tasks, and end-to-end test scenarios.</li></ul><p><br></p><p>Learn More at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/78" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/78</a></p>
<p><strong>*APPLICATION ONLY OPEN TO COLLEGE STUDENTS BASED IN CHINA*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>Software refactoring and restructuring is common in the open-source development of SONiC. Existing code structure may limit the adoption of new usage scenarios or protocol features, necessitating its refactoring into a better logical structure. For example, the ongoing RIB/FIB project intends to separate the RIB and FIB maintenance code in Zebra and move the latter down to SONiC’s fpmsyncd component. Since fpmsyncd resides in SONiC code space, it allows FIB to construct SONiC specific forwarding chain, and handle route convergence based on SONiC’s requirements.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>A central requirement in such refactoring is to ensure that behavior changes are exactly as expected. In the RIB/FIB example, it requires that normal executions must be equivalent before and after the refactor. The objective of this mentorship is to devise a systematic approach to validate behavioral equivalence during SONiC refactoring. More specifically, it involves applying formal methods to mathematically describe the intended behavior, compare two distinct setups, and generate comprehensive tests to ensure the consistency before and after the refactor. This will serve as an exemplar of the formal-methods-based correctness paradigm in production code development.</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>Abstract formal models describing expected behavior of the relevant RIB/FIB operations.</li><li>Testing infrastructure that supports parametrized testing of individual modules and execution sequences across modules.</li><li>A test generation framework and the resulting high-coverage benchmark to validate the correctness of the RIB/FIB implementation.</li><li>*<strong>Program Term: Summer / Fall Term (May - November) 20 hours of work each week*</strong></li></ul><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Familiarity with Python and C/C++</li><li>Basic understanding of network forwarding and routing</li><li>Comfort with hands-on systems work under technical guidance, including system setups, trouble shooting, etc.</li><li>Strong communication skills</li></ul>
<p>This project aims to implement a new privacy-preserving token driver for the Hyperledger Fabric Token SDK. The architecture will follow the blueprint established in the paper "Privacy-preserving auditable token payments in a permissioned blockchain system" (Androulaki et al.), which outlines a token management system tailored for enterprise networks that requires binding tokens to user identities while supporting fine-grained auditing functionalities for AML/KYC compliance.</p><p><br></p><p>While the original paper relies on specific zero-knowledge proofs and commitments, this mentorship project will adapt the cryptographic backend to utilize zk-SNARKs via gnark, a high-performance ZK-SNARK library written in Go by Consensys. The mentee will be responsible for designing the required ZK circuits for minting, transferring, and auditing tokens, and subsequently integrating these circuits into a fully functional token driver within the Fabric Token SDK framework.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Gain a comprehensive understanding of the Hyperledger Fabric Token SDK architecture and the role of token drivers.</li><li>Develop practical expertise in Zero-Knowledge Proofs (zk-SNARKs) and circuit design using the gnark library.</li><li>- Understand the cryptographic mechanisms behind privacy-preserving enterprise blockchains, including UTXO models, Pedersen commitments, and identity-bound token ownership.</li><li>Enhance skills in writing highly optimized, concurrent, and secure Go code for distributed systems.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>Fully functional gnark circuits implementing the logic for token issuance, private transfers, and auditor revelation as described in the blueprint paper.</li><li>A new ZK-SNARK token driver completely integrated into the Hyperledger Fabric Token SDK.</li><li>A comprehensive test suite, including unit and integration tests for the driver and circuits.</li><li>- Performance benchmarks evaluating proof generation times, verification times, and transaction throughput compared to existing FTS token drivers.</li><li>Technical documentation detailing the circuit design, driver architecture, and usage instructions.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/67" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/67</a></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><strong style="background-color: transparent; color: rgb(0, 0, 0);">Program Overview</strong></p><p><span style="background-color: transparent; color: rgb(31, 31, 31);">This proposal outlines a 12-week mentorship program focused on significantly enhancing the rule testing and Continuous Integration (CI) tooling for Minder's security policies. The project will primarily involve the go programming language, with secondary exposure to rego, python, and shell scripting. The successful completion of this project will provide Minder users with a robust, automated, and maintainable framework for ensuring the quality and correctness of custom security rules.</span></p><p><br></p><p><span style="background-color: transparent; color: rgb(31, 31, 31);">This opportunity is open for a single mentee with some previous GitHub and medium-sized project experience.</span></p><p><br></p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Program Goals</strong></p><p><span style="background-color: transparent; color: rgb(31, 31, 31);">The primary goals of this 12-week engagement are to:</span></p><p><br></p><ol><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Improve Rule Testing Tools: Develop a standalone testing command for Minder rules.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Robust Testing: Allow for the definition and execution of multiple distinct test cases against a single rule.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Focus on Local Execution: Tests should be able to execute locally without requiring network access to external resources.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Support Diverse Data Ingestion: Design the framework to accommodate tests for rules covering all current data ingestion methods: REST API, Git repositories, and declared </span><a href="https://docs.mindersec.dev/understand/data_sources" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(31, 31, 31);">data sources</a><span style="background-color: transparent; color: rgb(31, 31, 31);">.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Provide Automated CI Tooling: Implement CI workflows to automatically detect and run tests.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Update Existing Rules: Migrate and update existing tests within the github.com/mindersec/minder-rules-and-profiles repository to utilize the new framework.</span></li><li><span style="background-color: transparent; color: rgb(31, 31, 31);">Documentation and UX: Create documentation for the new tooling and address potential client-side UX issues related to testing.</span></li></ol><p><br></p><p><br></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>Open source projects face an urgent governance gap as AI coding tools (Claude Code, GitHub Copilot, Cursor, Qwen Code) act on codebases with no shared coordination layer, no policy enforcement, and no auditable trail. The result is PR floods, duplicate issue work, and maintainer burnout.</p><p><br></p><p>GitMesh is an LFDT-native multi-agent orchestration runtime that closes this gap. This mentorship will implement Phase 1 (GitHub/GitLab Forge Integration) and Phase 2 (Policy-as-Code Engine) — building the <code style="background-color: rgba(129, 139, 152, 0.12);">forge-sync</code> bidirectional webhook service, the <code style="background-color: rgba(129, 139, 152, 0.12);">policy-engine</code> OPA integration with YAML-to-Rego auto-compilation, an append-only audit log with policy enforcement metadata, and a three-view maintainer dashboard. Real infrastructure, deployed to a live LFDT lab.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Build a bidirectional webhook-based forge integration (GitHub/GitLab) with event-triggered agent wakeups.</li><li>Design a policy-as-code engine using OPA with YAML-to-Rego auto-compilation and real-time evaluation middleware.</li><li>Implement an append-only audit log capturing policy version and enforcement outcome for every agent action.</li><li>Build a maintainer approval dashboard (Active Agents, Pending Approvals, Audit Log) with mobile-first UX.</li><li>Learn AI agent coordination patterns — atomic checkout, budget enforcement, heartbeat scheduling.</li><li>Gain exposure to LFDT identity extension points (Hyperledger Identus, AnonCreds, Sigstore) planned for the future trust layer.</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ol><li>Forge Integration Service — Bidirectional GitHub/GitLab webhook receiver and outbound action service (post comment, add label, request review, close issue). Includes raw webhook storage and event-triggered agent wakeup support.</li><li>Policy Engine — OPA integration with YAML-to-Rego auto-compilation. Policy evaluation middleware injected into all agent heartbeats and API routes.</li><li>Audit Log Enhancement — <code style="background-color: rgba(129, 139, 152, 0.12);">policyVersion</code> and <code style="background-color: rgba(129, 139, 152, 0.12);">policyOutcome</code> columns on the activity log. Append-only, exportable as JSON/CSV, filterable by agent/action/time/outcome.</li><li>Three-View Maintainer Dashboard — Active Agents (status, budget), Pending Approvals (mobile-first), Audit Log (policy filtering).</li><li>Default Policy Template Library — Five ready-to-use YAML rulesets (no-merge-without-approval, no-CI-modification, security-advisory-gate, budget-hard-stop, triage-scope-limits).</li><li>Documentation — Architecture diagram, developer onboarding guide, YAML policy authoring reference, end-to-end test scenarios.</li></ol><p><br></p><p>Learn More at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/81" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/81</a>.</p>
<p>In standard cryptography, a single compromised key means total failure. Threshold Signing Schemes (TSS) mitigate this by distributing "shares" of a key across n participants, requiring a minimum threshold t participants to engage into the protocol to generate a signature. While the Lockness ecosystem already has a CGGMP24, a threshold ECDSA protocol, the <a href="https://eprint.iacr.org/2023/765.pdf" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">DKLs23</a> protocol presents different features and performance, and unlocks new use-cases.</p><p><br></p><p>In this project, your goal is to transform a formal description of the protocol from the <a href="https://eprint.iacr.org/2023/765.pdf" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">DKLs23 paper</a> into the code utilizing <code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://docs.rs/round-based/latest/round_based/" rel="noopener noreferrer" target="_blank">round-based</a></code>, a framework for TSS protocols, and <code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://docs.rs/generic-ec/latest/generic_ec/" rel="noopener noreferrer" target="_blank">generic-ec</a></code>, a type-safe library for elliptic-curve arithmetics.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Deep Dive into MPC & Threshold Primitives: Transition from theoretical knowledge of cryptography to implementing complex Multi-Party Computation (MPC) protocols, and gain a first-hand understanding of how t-out-of-n security is maintained mathematically.</li><li>Rust Development in the Lockness Ecosystem: Master high-performance, memory-safe programming by contributing to the Lockness ecosystem, specifically using the <code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/generic-ec" rel="noopener noreferrer" target="_blank">generic-ec</a></code> library for efficient and type-safe elliptic curve operations.</li><li>Modern Distributed Programming: Learn to write asynchronous code via the <code style="color: rgb(9, 105, 218); background-color: rgba(129, 139, 152, 0.12);"><a href="https://github.com/LFDT-Lockness/round-based" rel="noopener noreferrer" target="_blank">round-based</a></code> framework to manage complex network interactions.</li><li>From Paper to Production: Develop the ability to translate academic research into reliable, auditable, high-quality code, bridging the gap between "whitepaper math" and "real-world software".</li><li>Production-Grade Workflow: Experience a professional development lifecycle where cryptographic code is subject to rigorous peer reviews and testing to ensure maximum security. Learn the discipline required to build cryptographic libraries where every line of code must be verified for both correctness and security.</li></ul><p><br></p><h3>Expected Outcome and Deliverables</h3><p>A library that implements DKLs23 protocol.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/58" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/58</a></p>