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>This project aims to explore how KubeEdge can support real-world embodied AI applications, where intelligent devices such as robots, inspection systems, or autonomous mobile platforms need to perceive, process, and respond in edge environments.</p><p>The mentee will select a representative embodied AI scenario and build an end-to-end edge-cloud collaboration solution with KubeEdge. The solution should cover device or data source access, edge-side data processing, lightweight AI inference, cloud-edge synchronization, and system behavior under unstable network conditions.</p><p>Through this project, the community will gain a reproducible reference implementation that demonstrates how KubeEdge can be used as the infrastructure foundation for embodied AI workloads.</p><p><br></p><p>Expected Outcome:</p><p> - Select a specific scenario related to embodied intelligence.</p><p> - Set up the KubeEdge edge-cloud environment: complete the deployment and configuration of CloudCore and EdgeCore, enable edge node access, and verify status synchronization and basic communication capabilities.</p><p> - Implement a closed loop for device access and edge AI inference: complete device or data source access, data collection, device status modeling, deployment of edge-side AI inference services, and inference result reporting.</p><p> - Verify edge-cloud collaboration and edge autonomy: implement cloud-side model delivery, configuration updates, and data aggregation, and verify continuous edge operation and recovery synchronization under weak network or disconnected scenarios.</p><p> - Provide reproducible engineering assets and evaluation documents, including architecture diagrams, KubeEdge configuration files, deployment and validation scripts, sample data, running instructions, and performance and reliability evaluation reports.</p><p><br></p>
<p>Markdown provides a great ability to format messages and write structured documents using plain text format.</p> <p>Zulip uses two different markdown processors: for the backend, it is <a href="https://github.com/Python-Markdown/markdown" target="_blank">Python-Markdown</a> and for the frontend, it is <a href="https://github.com/markedjs/marked" target="_blank">marked.js</a>.</p> <p>While the backend markdown processor is highly extensible but the current frontend markdown processor doesn’t allow the same. Moreover, it is not upgradeable because of the Zulip customisations.</p> <p>The goals of this project are:</p> <ol> <li>Refactor the frontend-markdown processor with CommonMark parser.</li> <li>Make the same extensible for Zulip’s custom features like @-mentions.</li> </ol> <p>I’ll take the reference from <a href="https://github.com/commonmark/commonmark.js" target="_blank">commonmark.js</a> to write the CommonMark parser for our frontend-markdown processor. And to make it extensible, I'll use the upstream <a href="https://github.com/markedjs/marked" target="_blank">marked.js</a>.</p> <p>In parallel to this, I’ll focus on works in the markdown area. Integrating them with the Zulip will help to increase the overall users’ experience. The list of them are:</p> <ol> <li><a href="https://github.com/zulip/zulip/issues/17971" target="_blank">Add support for link shortener</a></li> <li><a href="https://github.com/zulip/zulip/issues/2401" target="_blank">Re-enable backslash escape inline pattern</a></li> <li><a href="https://github.com/zulip/zulip/issues/2183" target="_blank">Add support for online mentions</a></li> <li><a href="https://github.com/zulip/zulip/issues/13746" target="_blank">Add support for importing avatar from GitHub on account creation</a></li> </ol>
Today, with Ubuntu increasingly adopting Snap packages, Uyuni currently lacks support for managing these applications. This project proposes adding native Snap support to Uyuni, including install, update, remove, and channel management. By extending Uyuni’s capabilities to cover Snap, this work fills a key gap and ensures continued relevance for Ubuntu system management. I explored how Uyuni manages CVE audits and package upgrades for Ubuntu systems. Initially, Uyuni connects to client machines via SSH to install and register the Salt Minion. Once set up, all communication occurs through Salt’s remote execution system, eliminating the need for SSH. Salt gathers package data using grains, pillars, and custom modules, which Uyuni then compares to its centralized SUSE Manager database. For CVE auditing, Uyuni fetches security metadata (e.g., CVEs, OVAL data) from upstream sources like Ubuntu Security Notices and stores it in a PostgreSQL database. When Salt reports installed packages, Uyuni analyzes the data and generates patch or upgrade recommendations. APT repositories are mirrored into structured software channels, allowing clients to receive updates without direct internet access. Building on this workflow, I propose extending Uyuni to support Snap packages. While Snap lacks structured CVE metadata, we can implement a version-based upgrade system: Uyuni retrieves the latest Snap versions from the Snap Store and compares them to client versions reported via Salt, suggesting upgrades when newer versions exist. To support airgapped environments, we can pre-download .snap and .assert files on a connected system and distribute them through Uyuni’s software channels. Additionally, to manage storage and stability, Uyuni admins can choose which Snap channels (stable, beta, etc.) to mirror—defaulting to stable. Deliverables: Support Snap auditing, lifecycle management, airgapped environments, testing/validation, and user documentation in Uyuni.
Frameworks like PennyLane and Qiskit handle circuit construction and simulation well but provide almost no tools for measuring the quantum resources a circuit uses. No unified library exists to assess profiling entanglement, magic, or Bell nonlocality. I propose a PennyLane-based library computing four resource classes through a single resource_profile() API: entanglement (Meyer–Wallach, Von Neumann entropy, concurrence), magic (Stabilizer Rényi Entropy), mana (discrete Wigner negativity for qudits), and Bell nonlocality (CHSH values). Since PennyLane QNodes are differentiable, the measures inherit gradient access for tracking resource shifts during training. I also propose benchmarking across QAOA for MaxCut, Quantum Phase Estimation, VQE for molecular ground states (H₂, LiH), and quantum autoencoders for BSM event detection following Duffy et al. (arXiv:2407.07961). The study would record resource trajectories per epoch and test whether the resource decrease Duffy et al. observed generalizes, via Spearman correlations and Mann–Kendall trend tests. This project grows out of my prior work. My Quantum Encoding Atlas library (DOI: 10.5281/zenodo.18780936) benchmarks 16 encodings across PennyLane, Qiskit, and Cirq, and my 12 QMLHEP15 evaluation tasks span quantum circuits, GNNs, equivariant QNNs, RL for PQC optimization, and contrastive learning. Running those benchmarks I identified SRE as a missing diagnostic, which inspired me towards this project. Deliverables: 1. Python package on PyPI with entanglement, magic, mana, and nonlocality modules. 2. Circuit profiler for epoch-level resource tracking. 3. Benchmarking dataset for all four algorithms. 4. Resource–performance correlation analysis. 5. API docs and Jupyter notebook tutorials. 6. Two blog posts per ML4SCI requirements. Stretch: tensor network SRE approximations beyond 10 qubits and integration with Knipfer et al.'s agent-based VQC design (arXiv:2602.19387).
<p>Global post-trade settlement infrastructure remains fragmented across incompatible ledger implementations, jurisdictional compliance regimes, and asset-class-specific token schemas — creating systemic friction at the intersection of programmable finance and institutional market microstructure. This project conducts an open, community-driven research inquiry into the design space for a protocol-agnostic token framework within the LF Decentralized Trust ecosystem, exploring how composable token primitives may serve as a convergence layer across heterogeneous post-trade settlement rails. All research outputs, findings, and prototypes will be contributed openly to the LF Decentralized Trust community under applicable open-source licenses, with no implied endorsement or proprietary claim by any contributing organization.</p><h3>Learning Objectives</h3><p>The mentee will survey existing tokenization frameworks, identify gaps in interoperability and compliance metadata propagation, and develop exploratory prototypes to inform community discussion around open standards for post-trade infrastructure within the LF Decentralized Trust ecosystem.</p><h3>Expected Outcome and Deliverables</h3><ul><li>A Research Report documenting a comparative survey of existing tokenization frameworks, proposed schema considerations, and community recommendations for token base types, behaviors, and metadata — contributed as an open draft for community review.</li><li>An Exploratory Prototype — a series of illustrative smart contract examples (Solidity or Chaincode) demonstrating potential implementation patterns across representative use cases, intended for research and educational purposes only.</li><li>A Community Whitepaper presenting findings, open questions, and suggested directions for post-trade token framework adoption — offered as a contribution to broader community discourse with no prescriptive or regulatory guidance implied.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/88" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/88</a></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>Kuadrant's MCP Gateway uses an Envoy external processor (ext_proc) to parse MCP JSON-RPC requests, extract metadata, rewrite request bodies, and route tool calls to backend MCP servers. This works but adds latency via a gRPC hop per request and requires maintaining custom MCP protocol parsing logic. Envoy has been rapidly adding native MCP support, as of v1.38, the Envoy MCP filter can parse MCP messages, populate dynamic metadata for downstream RBAC/ext_authz filters, handle session management, support SSE and Streamable HTTP transport, and aggregate multiple backend MCP servers. A previous investigation rejected the Envoy MCP filter due to missing body modification support, limited method coverage, and no aggregation, but the filter has since evolved considerably. This project will perform a fresh evaluation, produce a design document mapping each ext_proc responsibility to native Envoy capabilities, identify gaps (particularly around request body rewriting for tool prefix stripping and dynamic metadata consumption by Authorino), build a proof-of-concept demonstrating the native filter approach, and propose an incremental migration path. The mentee will work closely with mentors on the design, validate assumptions through prototyping with standalone Envoy, and engage with both the Kuadrant and Envoy communities.</p><p><br></p><p>Expected Outcome:</p><p> - Design document covering capability mapping of each ext_proc responsibility to Envoy MCP filter features, body modification strategy, dynamic metadata vs header trade-offs for Authorino integration, federation/aggregation comparison, session management analysis, and Istio version dependency chain</p><p> - Proof-of-concept demonstrating Envoy MCP filter parsing requests and populating metadata, downstream authorization consuming that metadata, and tool routing to multiple backends</p><p> - Clear identification of what still requires custom code after migration</p><p> - Proposed target architecture and incremental migration plan</p><p> - E2E tests validating the prototype against existing test scenarios</p><p> - Documentation of Istio version requirements and feature gates needed</p><p><br></p>
<p>Fablo is a tool mostly used for local development and in CI. It starts a Hyperledger Fabric network from a single configuration file, and supports various features that makes the development easier (REST API, network snapshots, advanced topology configuration, hooks, etc). It supports Hyperledger Fabric in versions 2.x and 3.x. Last year we were able to ensure feature parity between versions.</p><p><br></p><p>The target user of Fablo is the developer who works with the local Hyperledger Fabric network to either experiment with various topologies or work on contracts. The goal of this internship is to improve the overall developer experience by:</p><p><br></p><ul><li>Ensuring we have up to date and more approachable documentation, kept up to date with the help of AI CI workflows.</li><li>Improving Fablo distribution by supporting npm package along with existing Docker image distribution.</li><li>Resolving friction that is related to random errors, or slow responsiveness of the network setup.</li></ul><p><br></p><p>While a significant part of the proposal is improving the documentation Fablo, the most focus is on automating the process of keeping documentation up to date. This is why the primary focus of this proposal is coding.</p><h3><br></h3><h3>Learning Objectives</h3><ul><li>Designing and implementing GitHub Actions workflows</li><li>Using AI agent workflows in real use cases</li><li>Creating concise and approachable documentation</li><li>Debugging and resolving complex issues</li><li>Experience with Hyperledger Fabric network topology, setup and configuration</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>GitHub Pages with documentation</li><li>GitHub Actions using AI workflows to keep the documentation up to date</li><li>Agent skill file for Fablo</li><li>An additional channel of distributing Fablo (npm)</li><li>PRs with fixes towards reducing developer friction</li></ul><p><br></p><p>Learn More at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/84" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/84</a>.</p>
<p>*THIS APPLICATION IS ONLY OPEN TO COLLEGE STUDENTS BASED IN CHINA*</p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>BGP Link State (BGP-LS) is a northbound information exchange protocol extension. It allows external clients to subscribe to and collect link-state data (topology, traffic engineering metrics, segment routing SIDs, etc.). Originally designed as an export mechanism, BGP-LS is being increasingly used as a critical feed-back component in the operation and management of cloud network infrastructures. For example, TE controllers may rely on such information to respond to real-time connectivity and traffic status. Thus, the accuracy and reliability of BGP-LS is of foundational importance.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The objective of this mentorship is to develop systematic tests and validations for the BGP-LS implementation. More specifically, it needs to address complexities at various levels to achieve high coverage of the implementation. For example, at the high level, the stateful nature of the protocol extension itself, as well as the dynamic, disaggregated changes in a router's internal states, require thorough exploration of the handling of diverse interaction scenarios and even inconsistent states. At the low level, data processing utilities, such as the parsing of internal routing data formats, also requires systematic testing to validate the handling of both normal and abnormal data. </p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><p>A set of formal models describing both the expected high-level interactions and low-level processing logics of BGP-LS.</p><p>Benchmarks containing diverse interaction sequences and input data, providing comprehensive behavior and code coverage.</p><p>Testing infrastructures to execute, evaluate, and refine these tests.</p><p><strong>*Program Term: Summer - Fall (May - November) 20 hours of work each week*</strong></p><p><br></p><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Proficiency in Python and C/C++</li><li>Basic knowledge of IP networking and routing</li><li>Basic understanding of distributed systems and concurrency</li><li>Ability to navigate and understand complex codebases</li></ul>
<p>*<strong>APPLICATION ONLY OPEN TO COLLEGE STUDENTS LOCATED IN INDIA*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p> </p><p>SONiC currently exposes per-interface traffic counters, but operators lack a simple mechanism to quickly identify which interfaces are carrying the highest traffic at any given time. In large-scale deployments, manually scanning counters is inefficient and error-prone.</p><p> </p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>The objective of this project is to design and implement a SONiC feature that displays the top N (default: 5) interfaces carrying the highest traffic. The feature will be exposed via the SONiC CLI and will leverage existing interface counters.</p><p> </p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><p>A new CLI command will be introduced to calculate and display the top interfaces based on real-time traffic rates. The implementation will read interface counters from SONiC databases, compute traffic deltas over a configurable interval, sort interfaces by total throughput, and present the top results in a user-friendly format. <strong>*SUMMER SEMESTER EXPECTATION OF 40 HOURS OF WORK A WEEK*</strong></p><p><br></p><p><strong>Key Features</strong></p><p><br></p><p>- Display top 5 interfaces by traffic (RX + TX)</p><p>- Configurable sampling interval</p><p>- JSON output option for automation</p><p>- Minimal performance overhead</p><p><br></p><p><strong>Technology Scope</strong></p><p><br></p><p>The implementation will be done in Python and integrated into the sonic-utilities CLI. Interface counters will be read from COUNTERS_DB. Traffic rates will be computed using delta-based calculations between two samples.</p><p><br></p><p><strong>Expected Outcome</strong></p><p>At the end of the project, SONiC users will have a simple and effective tool to quickly identify high-traffic interfaces, improving troubleshooting and capacity planning.</p><p> </p><p><strong>Recommended Qualifications</strong></p><p> </p><p>1. Knowledge about one of the common programming language: python/java/c++/golang</p><p>2. Basic understandings of Linux networking stack</p><p>3. Familiarity of containers</p>
<p><strong>*APPLICATION ONLY ACCEPTING US BASED COLLEGE STUDENTS*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>As an Internet-facing networking protocol, BGP is one of the most critical components of cloud-scale networks. It enables routing information exchanges between a cloud network and the broad Internet, and incorrect behavior could devastate the connectivity of entire regions. Among many vulnerabilities, the proper handling of malformed packets is particularly important due to the propagation mechanisms of BGP. In real production network, a single mis-handling could result in cascading BGP message floodings across entire regions, degrading services or even causing network outages.</p><p><br></p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><p>Currently, high-level BGP behaviors are well-defined through various RFCs. However, low-level details, such as the validation and handling of malformed packets, are often under-specified. Current testing relies on ad-hoc fuzzing or manual test cases, which may miss subtle state-machine interactions that require specific input combinations.</p><p><br></p><p>The objective of this mentorship is to apply formal methods to systematically validate the handling of malformed packets by concrete BGP software implementations. Unlike traditional approaches, formal methods use mathematical logic to systematically explore diverse behaviors triggered by different input combinations, providing comprehensive validation coverage.</p><p><br></p><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>A formal specification that describes high-level BGP interactions.</li><li>A set of implementation-agnostic safety invariants derived from the above high-level model. They ensure that invariant-abiding interactions will not cause cascading effects on neighboring BGP devices.</li><li>A reusable framework that applies off-the-shelf formal methods tools to systematically test concrete BGP implementations against the above invariants.</li><li>A benchmark suite of validated malformed packet scenarios with coverage metrics.</li><li><strong>SUMMER / FALL TERM (20~ HOURS OF WORK EACH WEEK)</strong></li></ul><p><br></p><p><br></p><p>Recommended Qualifications</p><p><br></p><ul><li>Familiarity with Python and C/C++</li><li>Basic understanding of networks and routing</li><li>Good analytical skills</li></ul><p><br></p>
<p>Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This project focuses on expanding Meshery Relationships across a wide range of technologies, including Kubernetes and major cloud providers, to better model their interactions and improve user insights. There is a growing need to accurately model these relationships to provide better insights and control over deployments.</p><p><br></p><p> The next phase focuses on Cloud Solution Architecture through workload design by creating and publishing Meshery designs that use the newly developed relationships to represent real-world deployments. These designs will be turned into structured tutorials with hands-on labs using Meshery Playground, offering step-by-step guidance and interactive learning. All content will be reviewed by maintainers and published in Meshery’s official documentation</p><p><br></p><p>Responsibilities:</p><p> - Research and Analyze Technologies: Dive deep into various cloud-native technologies (e.g., different compute services, databases, messaging systems, network services, etc.) to understand their components and how they interconnect.</p><p> - Develop Relationship Definitions: Create and contribute relationship definitions, typically in JSON or YAML format, to the Meshery models.</p><p> - Model Inter-Technology Interactions: Focus particularly on defining relationships between components from different technologies (e.g., how a Kubernetes deployment relates to an AWS RDS instance, or how a Linkerd service interacts with a Prometheus monitoring component).</p><p> - Document New Relationships: Clearly document the newly defined relationships, their purpose, and how they are represented within Meshery designs, contributing to the official Meshery documentation.</p><p> - Create and publish designs that use newly developed relationships.</p><p> - Create and publish hands-on tutorials using Meshery Playground, featuring step-by-step guides and interactive labs that enable learners to apply concepts without the hassle of any configuration.</p><p><br></p><p>Expected Outcome:</p><p> - A multitude of new intra- and inter-service relationships defined across AWS, Azure, and GCP.</p><p> - Creation and publishing of real-world workload designs that represent cloud solution architectures using the newly defined relationships.</p><p> - Tutorials reviewed by various project maintainers and then published in guides/tutorials.</p><p> - Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.</p><p><br></p>
<p>KubeVela's workflow engine and config management layer have two long-standing production gaps that this mentorship will close together. First, the `request` workflow step has no native way to source HTTP headers (bearer tokens, API keys, basic auth) from Kubernetes Secrets — users wanting to call authenticated APIs are forced to hardcode credentials directly in the workflow definition, where they end up visible in `kubectl get` output and Git history. On top of that, attempts to interpolate values into the `header` map using Go templates or CUE string interpolation regularly conflict with native CUE syntax, producing un-rendered strings or silent execution failures. Second, KubeVela's Config Management today stores `ConfigTemplate`s as labeled ConfigMaps (`config-template-*` prefix) and `Config`s as labeled Secrets — there are no proper Kubernetes API types (`kubectl get configs` returns nothing meaningful), and all CUE schema and `validation.$returns` checks run client-side in the `vela` CLI. Configs created through any other path (workflow steps, VelaUX, direct `kubectl apply`) bypass validation entirely, so the same template enforces different rules depending on the entry point. The mentee will tackle both. The first deliverable extends the HTTP provider in `kubevela/workflow` with a `headerFromSecret` field that resolves values from Kubernetes Secrets natively in Go (mirroring how the same provider already handles Secrets for `tlsConfig`), and exposes it as a first-class CUE parameter — bypassing the templating layer entirely. The second introduces a proper Kubernetes API group, `config.oam.dev/v1alpha1`, with `ConfigTemplate` and `Config` CRDs, event-driven controllers built on controller-runtime, and validating admission webhooks that move CUE validation server-side. Sensitive properties never live in the CRD — they sit in a separate Secret referenced via `propertiesFrom.secretRef`. A dual-read controller preserves full backward compatibility: legacy ConfigMap templates, old CLI versions, and existing Secret-based configs continue to work without disruption. Together, the two deliverables harden KubeVela's HTTP integration surface and modernize its configuration layer into a Kubernetes-native, GitOps-friendly API.</p><p><br></p><p>Expected Outcome:</p><p> - New `HeaderFromSecret` field on the `Request` struct in `pkg/providers/http/http.go` (kubevela/workflow), with native Secret resolution inside `runHTTP()` mirroring the existing `getTransport()` TLS pattern</p><p> - Updated `request.cue` definition in kubevela/kubevela exposing `headerFromSecret` as a parameter, with namespace defaulting to `context.namespace`</p><p> - New `config.oam.dev/v1alpha1` API group with `ConfigTemplate` and `Config` CRDs, DeepCopy, and scheme registration</p><p> - `ConfigTemplateReconciler` that parses CUE templates and writes the generated OpenAPI schema to `status.schema`</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>*APPLICATION ONLY OPEN TO COLLEGE STUDENTS BASED IN THE UNITED STATES*</strong></p><p><br></p><p><strong>Problem Statement</strong></p><p><br></p><p>BGP Link-State Protocol (BGP-LS) is a critical protocol for modern network management and SDN-style controller integration, enabling the distribution of network topology information. Currently, SONiC's BGP-LS implementation lacks comprehensive CLI tools for configuration and monitoring, making it difficult for network operators to effectively deploy and troubleshoot BGP-LS in production environments. Additionally, there is insufficient testing infrastructure to validate BGP-LS functionality in complex multi-node topologies.</p><p>This mentorship program aims to address these gaps by developing a complete CLI interface for BGP-LS operations and establishing a robust 7-node testing framework based on vSONiC instances. This will significantly improve SONiC's BGP-LS usability and reliability, making it production-ready for enterprises and service providers who rely on topology discovery for traffic engineering and network automation.</p><p><br></p><p><strong>Mentorship Objectives</strong></p><p><br></p><ul><li>Develop a comprehensive CLI interface for BGP-LS configuration, monitoring, and troubleshooting in SONiC</li><li>Design and implement a 7-node test topology to validate BGP-LS functionality in complex network scenarios</li><li>Create automated test cases covering BGP-LS neighbor establishment, topology advertisement, and failure scenarios</li><li>Document CLI usage and testing procedures for community adoption and future development</li></ul><p><br></p><p><strong>Expected Outcomes and Deliverables</strong></p><p><br></p><ul><li>Complete BGP-LS sonic-cli implementation with commands for neighbor configuration, status checking, and topology visualization</li><li>Functional 7-node test environment with automated deployment scripts and topology configurations</li><li>Comprehensive test suite covering at least 15-20 BGP-LS scenarios including normal operations and edge cases</li><li>Technical documentation including CLI user guide, test topology design document, and contribution guidelines for future enhancements</li><li>Merge CLI codes into SONiC repo</li><li><strong>Program Length: Summer / Fall Term (May - November) 20 hours of work each week*</strong></li></ul><p><br></p><p><strong>Recommended Qualifications</strong></p><p><br></p><ul><li>Proficiency in Python and/or C++ programming</li><li>Understanding of BGP routing protocols and network topology concepts</li><li>Familiarity with Linux CLI development and command-line interface design patterns</li><li>Experience with network testing frameworks (pytest, ansible Framework) or willingness to learn</li><li>Basic knowledge of SONiC architecture or similar network operating systems</li><li>Strong documentation and communication skills</li></ul>
<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>KubeVela's native Helm provider currently uses a plain `sync.Map` to cache fetched charts on the controller, keyed by chart-version with TTL-based expiry (24h immutable / 5m mutable). Because the reconciler is stateless and re-renders every Application on every 5-minute resync, this cache sits on the hot path for every reconcile. At scale — 100+ Applications consuming different charts — the unbounded `sync.Map` grows monotonically until the controller pod is OOM-killed. Parsed `*chart.Chart` Go objects are 2–10MB each, so 200 cached charts can mean 1–2GB of memory with no eviction until TTL expires. Deleted Applications' charts also linger for the full TTL window, and there is no mechanism to reclaim memory under pressure. This mentorship will design and implement an LRU eviction layer with configurable byte-size limits, packaged as a generic, Helm-agnostic cache in `pkg/utils/cache/` so it can be reused by the workflow engine and other providers. The mentee will build a generic `LRUByteStore` on top of `hashicorp/golang-lru/v2` with per-entry TTL, byte accounting, and three eviction triggers: synchronous byte-pressure on `Put`, lazy TTL check on `Get`, and a periodic background sweep. The Helm provider will switch from caching parsed `*chart.Chart` objects to compressed `.tgz` bytes (~20–25× memory reduction), with `chartutil.Save` / `loader.LoadArchive` handled in the provider so the cache stays opaque. New controller flags (`--helm-cache-max-bytes`, `--helm-cache-sweep-interval`) will be wired through Helm chart values, and the immutable-version TTL extended from 24h to 30d now that LRU handles memory pressure. `OnEvicted` callbacks will feed Prometheus metrics for hits, misses (by reason), and current cache bytes. The result is a production-ready, reusable cache package that closes a real OOM risk in KubeVela deployments today, with hands-on exposure to Kubernetes controller patterns, Go concurrency, Helm internals, and CUE-driven configuration.</p><p><br></p><p>Expected Outcome:</p><p> - Generic `LRUByteStore` package in `pkg/utils/cache/` built on `hashicorp/golang-lru/v2`, with per-entry TTL, byte accounting, byte-pressure eviction on `Put`, lazy TTL check on `Get`, and a periodic background sweep</p><p> - Helm provider migration from in-memory parsed `*chart.Chart` objects to compressed `.tgz` bytes (~20–25× memory reduction), with `chartutil.Save` / `loader.LoadArchive` encapsulated in the provider so the cache remains opaque</p><p> - New controller flags `--helm-cache-max-bytes` (default 256MB) and `--helm-cache-sweep-interval` (default 60s), wired through Helm chart values; immutable-version TTL extended from 24h to 30d</p><p> - Prometheus metrics fed by `OnEvicted` callbacks: cache hits, misses (by reason: expired/evicted/absent), and current cache bytes</p><p> - Ginkgo/Gomega test suite covering TTL expiry, byte-pressure eviction order, oversized entries, concurrent access, OnEvict callback correctness, and clean goroutine shutdown</p>
<p>AI agents can't move between platforms. When a user switches runtimes, their agent's memory, personality, and learned behavior disappear, locked into whatever system created them. There's no open standard for encrypting and exporting an agent's cognitive state.</p><p><br></p><p>Soul Protocol defines a <code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code> file format: an encrypted, portable container for agent identity and memory. It provides core primitives (create, read, write, export, import, encrypt, verify) without prescribing personality models, memory backends, or domain structures.</p><p><br></p><p>This project implements the encryption and portability layer: AES-256-GCM encrypted <code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code> file export/import, machine-derived key management, digital signature verification on import, and a cross-runtime test suite that validates <code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code> files across PocketPaw, LangChain, and CrewAI.</p><p><br></p><p>Reference implementation: <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/github.com/pocketpaw/pocketpaw" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">PocketPaw</a>, 533+ stars, 3,200+ PyPI downloads and growing, 31 contributors, 2,000+ tests, 7-layer security architecture with Guardian AI.</p><p>Academic context: "Everything is Context" (arXiv:2512.05470) formalizes context engineering for agents but treats them as stateless tools. Soul Protocol adds a persistent identity layer, portable, encrypted, and owned by the user.</p><p><br></p><h3>Learning Objectives</h3><ul><li>Understand encryption primitives for portable file formats (AES-256-GCM, PBKDF2 key derivation) and how they apply to identity systems</li><li>Study protocol design principles for thin open standards, looking at how MCP and W3C DID succeeded through minimal interfaces</li><li>Build cross-runtime compatibility layers in Python targeting multiple agent frameworks (PocketPaw, LangChain, CrewAI)</li><li>Practice test-driven development with 90%+ coverage on security-critical code</li><li>Write technical specifications and documentation for an open standard</li></ul><h3><br></h3><h3>Expected Outcome and Deliverables</h3><ul><li>Encrypted <code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code> file format specification (AES-256-GCM, machine-derived PBKDF2 keys, Ed25519 signature verification)</li><li>Python SDK: <code style="background-color: rgba(129, 139, 152, 0.12);">soul.export(encrypted=True)</code> and <code style="background-color: rgba(129, 139, 152, 0.12);">soul.import(path, key)</code> with complete key management</li><li>Cross-runtime test suite validating <code style="background-color: rgba(129, 139, 152, 0.12);">.soul</code> portability across PocketPaw, LangChain, and CrewAI</li><li>Developer documentation, quickstart guide, and specification document</li><li>Blog post documenting the mentorship experience, technical decisions, and lessons learned</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/75 " rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/75</a></p>
<h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Purpose</span></h2><p><span style="color: rgb(0, 0, 0); background-color: transparent;">gittuf is a security layer for Git repositories, allowing for a security policy to be applied independently of the service the repository may be hosted on (e.g. GitHub, Gitlab, Bitbucket, etc…). The purpose of this project is to improve gittuf in several domains, such as functionality, usability, and ease of access for new users.</span></p><p><br></p><h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Goal</span></h2><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Improve gittuf's UI and UX</strong><span style="color: rgb(0, 0, 0); background-color: transparent;">: gittuf is currently driven primarily by a CLI-based workflow. The gittuf TUI is a work-in-progress UX improvement, where users instead interact with gittuf more akin to a traditional desktop program. The TUI is currently basic, and extending its functionality and improving its appearance so that it can be the primary way users interact with gittuf would be ideal.</span></p><p><br></p><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Enable temporary/time-limited approvals</strong><span style="color: rgb(0, 0, 0); background-color: transparent;">: There may be cases when a developer may need to exercise some discretionary authority and approve something in violation of the policy (e.g. a critical security patch at 4am may not be able to be approved by the full team required in policy). Adding approvals that will satisfy the policy for some duration of time (but not infinitely) would serve to improve this aspect of gittuf.</span></p><p><br></p><h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Desired Outcomes & Deliverables (1-2 mentees)</span></h2><h3><span style="background-color: transparent; color: rgb(67, 67, 67);">Improve gittuf's UI and UX</span></h3><p><span style="background-color: transparent; color: rgb(0, 0, 0);">This project should result in gittuf featuring a polished, first-class TUI, as well as improvements to gittuf's UX in the CLI and API.</span></p><p><br></p><h4><span style="background-color: transparent; color: rgb(102, 102, 102);">Deliverables</span></h4><ul><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Substantial improvements to the gittuf TUI, both functionally and aesthetically.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Supporting documentation for how to use the updated TUI.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Appropriate tests and internal improvements needed to support the upgraded TUI.</span></li></ul><p><br></p><h3><span style="background-color: transparent; color: rgb(67, 67, 67);">Add functionality to gittuf to enable temporary/time-limited approvals</span></h3><p><span style="background-color: transparent; color: rgb(0, 0, 0);">Some changes in a repository may need to violate the policy (e.g. a critical security patch needing to be released at 4am, and only one developer is available to approve changes at the time).</span></p><p><br></p><p><span style="background-color: transparent; color: rgb(0, 0, 0);">A variant of this feature is to allow for changes to be submitted to a repository that must still be reviewed by someone else at a later time. These changes should not be consumed until they are reviewed, but should not necessarily pose a problem for the repository’s policy.</span></p><p><br></p><h4><span style="background-color: transparent; color: rgb(102, 102, 102);">Deliverables</span></h4><ul><li><span style="background-color: transparent; color: rgb(0, 0, 0);">A new feature that enables temporary/time-limited approvals in gittuf, as described above.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Supporting documentation for how to use this new functionality in gittuf.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Sufficient tests to ensure the proper operation of this new feature.</span></li></ul><p><br></p>