Contribo
ProgramsOrganizationsProjectsProposal StudioResourcesOrbit AIDashboard
Login
Login
Contribov1.0

Your premium companion for discovering, matching, and tracking paid open-source mentorship programs and verified starter issues.

Product

  • Programs Directory
  • Orbit AI
  • User Dashboard

Resources

  • Guides & Resources
  • Proposal Studio

Community

  • GitHub Repository
  • Code of Conduct

Legal

  • Privacy Policy
  • Terms & Conditions
  • Cookie Policy
  • Accessibility Statement

Made with love bySubhranshu Sekhar Dash

© 2026 Contribo. Built for the global open-source community.

PlatformProjects

Explore Projects

Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.

Confused which project to choose or don't know which one you are most suitable to work on?

Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.

Match with Orbit AI
Filters Clear
3883 Projects Found
Sort by

ML-Driven Audio Intelligence for TableTalk

advanced
HumanAI•2026Varies

Ready to Apply?

Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.

Start Proposal
Proposal Status
0% ProgressNot Started
Accepted Proposals
3 SimilarView →
Proposal Guide
Tailored DocsOpen →
Checklist & Review
Readiness AuditCheck →
350h (Large)

Problem Statement In interactive tabletop environments, Game Masters (GMs) face significant cognitive load when managing audio assets during live narration. Manually searching for and triggering specific dramatic recordings often disrupts the immersive flow of the session. There is a need for an automated system that can understand narrative intent and retrieve assets without interrupting the storytelling process.Proposed Solution I plan to bridge the gap between raw audio data and narrative utility by developing an automated pipeline for the TableTalk ecosystem. Leveraging my background in Computer Science and Economics and experience in agentic AI frameworks, I will implement:Narrative Tone Classification: Using a machine learning framework to categorize voice recordings into distinct narrative states (e.g., Urgent, Calm, Fearful).Hybrid Semantic Retrieval: Creating a retrieval engine that combines structured filtering with semantic ranking to allow GMs to use natural-language queries.Real-Time Trigger Logic: Implementing stream-based keyword spotting to map a storyteller's live performance to environmental atmospheric effects like lighting and soundscapes.DeliverablesQuantized Inference Engine: A lightweight model optimized for on-device mobile execution to ensure low-latency narrative classification.Search & Retrieval Module: A high-fidelity interface for natural-language audio discovery.Atmospheric Bridge: A software component that translates identified narrative tones or keywords into external hardware triggers.Technical Documentation: A complete guide and implementation roadmap for integrating these modules into the TableTalk mobile application.This project combines technical machine learning rigor with a deep appreciation for narrative immersion, informed by my previous work in multi-genre game development and algorithmic optimization

pythonmachine learningc+++2
Student: meganho456
Code
Proposal

Differentiable Logic for Interactive Systems and Generative Music

intermediate
BeagleBoard.org•2024Varies175h (Medium)

This project aims to enable the development of models that are suitably efficient for use in real-time interactive applications on embedded systems such as the BeagleBone-based Bela. At the project's core is difflogic, a recent technique that employs sparsely-connected network composed of basic logic gates to obtain small models and fast inference. The core goal of the project is to enable a convenient workflow for developing difflogic models and running them on the Bela, with an expected workflow of developing and training models on a larger machine, followed by exporting the model to C and cross-compiling it for the BeagleBone - either the main CPU or the PRUs. To support this, I will develop wrappers for exporting compiled difflogic models for use in the languages supported on Bela (C++, Pure Data, SuperCollider, Csound). I will then build out integrations and applications of difflogic for the rapid development of useful audio models, exploring the possibilities for combining difflogic networks with DDSP (differentiable digital signal processing) and cheap/lightweight techniques and toolkits, "porting" well-known ML architectures to difflogic networks, and training difflogic networks to approximate the behavior of existing neural networks (knowledge distillation). I will develop example applications involving sound analysis, classification, and synthesis, and experiment with interactive machine learning. Finally, I will apply these techniques to a creative application inspired by work on bytebeat and sound matching: generating networks of logic gates to approximate sounds and exploring the space of such sound-generating networks. I will train difflogic gates to reproduce particular sounds, treating the entire network as a bytebeat-style audio-generating function of time. Lastly, I will build an interactive application to explore the space of sound-generating networks (e.g. by mutating or morphing networks) and visualize the execution of logic gate networks.

cpythonlinux+11
Student: Ian Clester
Code

renAIssance VLM OCR for 17th-Century Spanish with Targeted LLM Correction

beginner
HumanAI•2026Varies90h (Small)

Project Summary: end-to-end OCR for 17th-Century Spanish Text using VLMs and assisted correction by an LLM The project addresses the significant challenge of performing accurate Optical Character Recognition (OCR) on 17th-century Spanish printed and handwritten documents. These historical materials are difficult for standard OCR tools due to archaic vocabulary, orthographic variations, and visual degradation such as ink bleed-through and faded text. Proposed Solution consists of an end-to-end pipeline centered on the Qwen2.5-VL-7B vision-language model (VLM). My approach moves beyond simple off-the-shelf recognition by implementing a multi-stage adaptation strategy: - Language Adaptation: Using LoRA-style masked language modeling (MLM) on the CORDE and CODEA corpora to teach the model 17th-century linguistic patterns and abbreviations. - Supervised Fine-Tuning: Training the adapted model on ground-truth transcriptions from the RenAlssance and RODRIGO datasets. - Targeted LLM Correction: Implementing a confidence-gated correction layer. Unlike generic "wholesale" correction which often introduces hallucinations, this layer uses a smaller, historically-tuned LLM to fix only low-confidence spans identified by the OCR model. Key Deliverables: By the end of the project, I aim to deliver: - A Reproducible OCR Pipeline: A complete system capable of handling both printed and handwritten 17th-century Spanish text. - Targeted Correction Module: A historically-adapted module that improves transcription accuracy by focusing only on uncertain text segments. - Evaluation and Normalization Harness: A documented toolkit for consistent Character Error Rate (CER) and Word Error Rate (WER) assessment. - Ablation Studies: Detailed reports isolating the performance gains from each stage of adaptation (language, visual, and correction) to guide future contributors.

pythonmachine learningc+++2
Student: Tushar Tyagi
Code

AI Model Service Auto Selection by Modality

advanced
LibreHealth•2023Varies350h (Large)

The LibreHealth Radiology AI Model service aids radiologists with AI to produce fast and accurate medical diagnoses. It communicates with LibreHealth RIS module to output labels on DICOM viewer. Currently, CheXnet model is integrated to the AI Model service, but the proposal expands to apply other models to imaging modalities like Mammo, Head CT, Abdomen CT. The project aims to understand what radiologists need in terms of AI and implement it. The goal is to help radiologists perform better by implementing algorithms for new imaging modalities. To tackle the problem we start by looking at research that have looked deep into model architectures and methods that work well with imaging modalities, for example Alexnet have proven to work on modalities like Head CT. We then collect the imaging data necessary to train out models and also decide on the method of training like transfer learning on pretrained models or do we go ahead with training a model from scratch. Appropriate feature engineering and tuning will be part of the problem solving process. Once we establish a model to perform well on a modality we proceed to integrate the model to the AI Model service application. The deliverables will include - Collate information on data sources, methods and models that will be used for implementation and review with mentor(s) - For any modality, start with data preparation, feature engineering, training and evaluation until satisfactory performance is achieved. Here we will trial different augmentation techniques and hyperparameter tuning methods. - Integrate the model inferencing code and retraining code to the application for all modalities - Add methods to the Flask API to appropriately call the specific AI model for a modality. Modify existing methods as necessary so as to include the new AI models - Perform unit tests, integration tests, functional tests and end to end tests for the implementations. Necessary coding standards will be used.

mysqljavascriptjava+6
Student: Rohan Satya Isaac
Code
Proposal

Improving Integration of SW360 with FOSSology

advanced
SW360•2025Varies350h (Large)

Currently, SW360’s integration with FOSSology is limited to only basic functionalities using outdated endpoints namely, triggering scans and checking scan status. This results in inefficient workflows, redundant uploads, lack of flexibility in scanning configurations, and restricted report formats. It also misses opportunities for reuse of scan data and lacks user-level attribution and secure token handling. This project and proposal aims to refactor and extend SW360's FOSSology integration by utilizing the modern RESTful API (OpenAPI v2 spec) offered by FOSSology. It will enable advanced functionalities such as: 1. Direct Source Uploads via POST /uploads 2. Checksum-Based Search and Reuse using /filesearch 3. Selectable Scanning Agents (e.g., Nomos, Monk, Reuser) 4. Multi-Format Report Generation (SPDX, CycloneDX, etc.) 5. User-Specific Token Support for secure and auditable API interactions These enhancements will be implemented through a modular, secure, and scalable API integration layer in SW360, with robust error handling, polling mechanisms, and extensibility for future API versions. Deliverables: 1. REST API Refactoring of SW360's FOSSology connector using modern v2 endpoints. 2. Efficient File Upload System with token-based authentication and job initiation. 3. Checksum Reuse Logic to avoid duplicate scans and utilize FOSSology’s “Reuser” agent. 4. Configurable Scanning Agent Support exposed via backend APIs. 5. Support for Diverse Report Formats, download mechanisms, and metadata linking. 6. Secure Token Management for both server-wide and user-specific workflows. 7. Robust Error Handling, retry logic, audit logging, and performance tuning. 8. Comprehensive Testing, documentation, and CI/CD pipeline integration.

javareactcouchdb+1
Student: Ritankar Saha
Code
Proposal

ABI Compliance Reporting System

advanced
PostgreSQL•2025Varies350h (Large)

PostgreSQL introduced Server API and ABI Stability Guidance to help extension authors understand compatibility expectations. The policy ensures ABI stability between minor releases (e.g., 17.0 to 17.1) but allows changes in major versions. Currently, committers rely on manual reviews to enforce this, which occasionally leads to unintended ABI changes. A recent example occurred in PostgreSQL 17.1, where an ABI-breaking change was shipped and later reversed in 17.2. This incident highlights the need for an automated process to catch such issues before release. To enforce ABI stability, this project will monitor PostgreSQL’s repository across STABLE branches, detecting any ABI breakage early. Since ABI changes depend on system architecture, OS, and compiler, the tool will be developed as an extension to PostgreSQL Build Farm, leveraging its infrastructure to handle diverse configurations. Git receive hooks are unsuitable as PostgreSQL does not allow them due to repository performance concerns. As the frequency of commits on the PostgreSQL stable branches is very low, build farm’s cron based clients (animals) can simply compare the latest commit build(which it already does) with the latest release tag or the most recent minor release to get the ABI breakage, if any. The Libabigail suite (abidw, abidiff) will be used for ABI compliance checks, currently supporting GCC and Clang, with future expansion planned for other compilers. The system will generate ABI compliance reports on every run and will send to the build farm server and notify the community about breaking changes. This project will include the development of a Build Farm Client Perl Module that generates ABI compliance reports and report any ABI Breaks to the community. This project will strengthen PostgreSQL’s ABI stability process, preventing unintended breakages and ensuring smoother minor releases.

cpostgresqlperl+8
Student: Mankirat Singh
Code
Proposal

Agentic CI Pipelines - GitHub Action Workflow Overhaul (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Meshery's CI/CD infrastructure spans a large and growing collection of GitHub Action workflows that have accumulated technical debt - inactive workflows, insecure patterns, and duplicated logic. This internship has two phases: first, a comprehensive audit and restructuring of existing workflows; second, the introduction of [GitHub Agentic Workflows](https://github.github.com/gh-aw/) to bring Continuous AI capabilities to Meshery's repository automation. Agentic Workflows allow automation to be defined in plain markdown and compiled into guardrailed GitHub Actions that run AI agents (Copilot, Claude, Codex) on schedule or in response to events - enabling automated CI failure triage, PR analysis, issue management, documentation maintenance, and compliance scanning with minimal human intervention.</p><p><br></p><p>Recommended Skills: GitHub Actions workflow authoring, CI/CD concepts, YAML, supply chain security basics (secret hygiene, fork-safe triggers, pinned actions). Interest in AI-assisted automation is a plus.</p><p><br></p><p>Responsibilities:</p><p>&nbsp;- Audit all workflows in `meshery/meshery`, cataloging each by type, activity status, and identified issues (duplication, insecurity, staleness).</p><p>&nbsp;- Produce a structured report with prioritized remediation recommendations, then implement accepted changes - consolidating redundant workflows and hardening insecure patterns.</p><p>&nbsp;- Author workflow taxonomy definitions (security classification levels, workflow types) for the Meshery Build and Release docs.</p><p>&nbsp;- Design and contribute agentic workflow definitions using the `gh aw` framework - covering CI failure diagnosis, PR feedback summarization, issue triage, and documentation consistency.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Measurably reduced and consolidated workflow set with no inactive or redundant workflows remaining.</p><p>&nbsp;- Published audit report and workflow taxonomy added to docs.meshery.io.</p><p>&nbsp;- A suite of agentic workflow definitions (`.md` + compiled `.lock.yml`) committed to the repository, demonstrating Continuous AI applied to Meshery's software delivery lifecycle.</p><p><br></p>

TBA
Proposal

LFDT - Improving Hyperledger Solang Through Comparative Analysis with the Soroban Rust SDK Mentorship Project

Intermediate
•Varies175h (Medium)

<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&nbsp;<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>

TBA
Proposal

Add support for Fabric-X

Intermediate
•Varies175h (Medium)

<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>

TBA
Proposal

Adapter for AI and LLMs (2026 Term 2)

Intermediate
•Varies175h (Medium)

<p>Meshery is the open source cloud native manager that empowers platform engineers to design and operate infrastructure. As infrastructure complexity grows, the need for intelligent assistance becomes critical. This project focuses on developing and enhancing a dedicated AI Adapter and AI Connections for Meshery. This adapter serves as the bridge between Meshery’s core orchestration engine and various Large Language Models (LLMs). The goal is to enable "Natural Language to Infrastructure" capabilities, allowing users to describe their architectural intent (e.g., "Deploy a highly available Kubernetes cluster on AWS with Prometheus monitoring") and have Meshery auto-generate the visual topology and configuration manifests. The intern will work on decoupling the AI logic from the core platform, allowing users to "Bring Your Own Key" (BYOK)—supporting both cloud-based providers (OpenAI, Anthropic) and local inference runners (Ollama, LocalAI).</p><p><br></p><p>Recommended Skills:</p><p>&nbsp;- Proficiency in Golang (Go) is essential, as Meshery’s backend is written in Go.</p><p>&nbsp;- Familiarity with MCP Servers, REST APIs, LLM APIs (OpenAI, Vertex AI), local inference servers (Ollama).</p><p>&nbsp;- Basic understanding of Kubernetes, Docker, and Infrastructure-as-Code (IaC) concepts.</p><p>&nbsp;- Experience with REST, GraphQL, and gRPC.</p><p>&nbsp;- Nice to have: Experience with React (for frontend integration in Meshery UI).</p><p><br></p><p>Responsibilities:</p><p>&nbsp;- Co-design and implement the interface for the AI Adapter in Go to communicate with the Meshery Server.</p><p>&nbsp;- Implement support for connecting to local LLMs (via Ollama) to ensure data privacy for users who cannot send infrastructure data to the public cloud.</p><p>&nbsp;- Improve the "System Prompt" and context-window management to feed the LLM relevant data regarding Meshery Models (schema definitions) so the AI generates valid infrastructure configurations.</p><p>&nbsp;- Write unit and integration tests to ensure the reliability of the adapter.</p><p>&nbsp;- Create user guides on how to configure the adapter with different AI providers.</p><p>- Expected Outcome:</p><p>&nbsp;- A fully functional AI Adapter (or Connection) integrated into the Meshery ecosystem.</p><p>&nbsp;- Demonstrable capability for users to swap between at least two different LLM providers (e.g., OpenAI vs. a local Llama 3 model).</p><p>&nbsp;- Implementation of a feature where natural language queries result in a rendered design.</p><p>&nbsp;- Merged pull requests (PRs) including code, tests, and documentation.</p><p><br></p>

TBA
Proposal

SONiC OS Profiling Mentorship Project

Intermediate
•Varies175h (Medium)

<p>*APPLICATIONS ONLY OPEN TO US BASED COLLEGE STUDENTS*</p><p><br></p><p>1. Problem Statement</p><p><br></p><p>Today, SONiC KVM-based PR testing validates functional correctness (test pass/fail) but does not track resource consumption or performance characteristics over time. This creates several blind spots:</p><p><br></p><ul><li>Performance regressions (CPU spikes, memory leaks, excessive I/O) introduced by PRs go undetected until they reach production or nightly pipelines.</li><li>There is no historical baseline of resource utilization per feature branch, making it impossible to distinguish normal variance from genuine degradation.</li><li>Nightly test environments lack systematic profiling, so gradual performance erosion across releases is invisible until a tipping point is reached.</li><li>Root-cause analysis of production incidents is hampered by the absence of correlated profiling data from the CI/CD stage where the regression was introduced.</li></ul><p><br></p><p>Without a structured profiling database and automated anomaly detection, the team operates reactively—discovering performance issues in production rather than catching them at the PR gate.</p><p><br></p><p>2. Proposed Solution</p><p><br></p><p>Build an end-to-end performance profiling pipeline that runs alongside SONiC KVM-based test execution, stores results in a centralized database, and automatically flags regressions at the PR gate.</p><p><br></p><p>2.1 High-Level Architecture</p><p><br></p><p>The solution is composed of four core components that integrate into the existing CI/CD and nightly test workflows:</p><p><br></p><ul><li>Profiler Container – A lightweight Docker container packaging the community profiler (e.g., py-spy, perf, cProfile) that runs in sidecar mode alongside the SONiC KVM during test execution.</li><li>Profiling Database – A remote time-series/relational database (e.g., PostgreSQL + TimescaleDB or InfluxDB) that stores per-run profiling snapshots keyed by feature branch, commit SHA, test case, and timestamp.</li><li>Analysis Engine – A statistical analysis module that performs comparative, clustering, and outlier detection on profiling data to identify spikes against historical baselines.</li><li>PR Gate Integration – A CI pipeline step that queries the analysis engine after test completion and fails the PR if any metric exceeds the configured threshold.</li></ul><p><br></p><p>3. Mentorship Objectives</p><p><br></p><ul><li>Help the mentee learn about SONiC OS architecture, container ecosystem, and KVM-based testing infrastructure.</li><li>Help the mentee gain hands-on experience with performance profiling tools (py-spy, perf, pidstat) and statistical analysis techniques.</li><li>Help the mentee understand CI/CD pipeline integration and automated quality gates.</li><li>Work with virtual SONiC testbeds (vsonic) to develop and validate the profiling pipeline without physical hardware.</li><li><strong>This is a summer term program, Mentees are expected to work 40~ hours a week</strong></li></ul>

TBA
Proposal

Chaos Mesh Mentorship Project

Intermediate
•Varies175h (Medium)

A Chaos Engineering Platform for Kubernetes.

TBA
Proposal

Keptn Mentorship Project

Intermediate
•Varies175h (Medium)

Keptn is a message-driven control-plane for application delivery and automated operations

TBA
Proposal

Wagtail Live

intermediate
Django Software Foundation•2021Varies175h (Medium)

<p>High speed content delivery from a messaging app to a Wagtail site.</p>

pythondjango
Student: Tidiane
Code
Proposal

Optimisation of GeantV HPC workload balancing

intermediate
CERN-HSF•2017Varies175h (Medium)

<p>This is proposal for implementing suggested HPC aware infrastructure with workload balancer.</p>

pythonc/c++machine learning+6
Student: Vitalii Drohan
Code
Proposal

Liu Jiahui's applicantion for gnome-logs

intermediate
GNOME•2018Varies175h (Medium)

<p>Logs could currently update the view when new log messages are added to the journal.</p>

cpythonjavascript+5
Student: hello_world_0
Code
Proposal

Work through OpenTelemetry User Research Documentation and Implement Fixes

Intermediate
•Varies175h (Medium)

Implement the fixes suggested in the user research documentation to make this project more consumable for end users.

TBA
Proposal

Transformers Model Quantization Helper

Advanced
Hugging Face•2026Varies350h (Large)

Implement automated model quantization pipelines (GPTQ, AWQ) for faster edge-based model compilation.

pythonpytorch
Lysandre Debut, Sylvain Gugger
Code
Proposal

Markdoc Schema-Driven Interactive Component Extensibility

Intermediate
Stripe Open Source•2025Varies175h (Medium)

Extend the Markdoc abstract syntax tree engine with dynamic custom tags and AST validation hooks.

typescriptreactjavascript
Michael Shapiro
Code
Proposal

Improving WebRTC, Apache Camel and Jitsi

intermediate
Debian Project•2016Varies175h (Medium)

<p>ICE and TURN support for Jitsi, SIP message for Apache Camel, WebRTC server probe.</p>

cpythondjango+5
Student: Nik Vaessen
Code
Proposal

Applied AI Ethics Sandbox

Intermediate
Vertex Applied AI Hub•2026€2k–€4kStandard (~175h)

Create a diagnostic visualizer for testing LLM outputs against Bias and Fairness metrics defined by the EU AI Act.

pythontypescriptreact
Dr. Sofia Rossi, Lars van der Meer
Code
Proposal

Rust WebAssembly Security Sandbox Boundary Audit

Advanced
Mozilla•2025$7,000Full-Time (~350h)

<p>Develop automated security assertion benchmarks for WebAssembly memory boundary checks in SpiderMonkey engine.</p>

rustwebassemblycpp
Yury Delendik
Code
Proposal

EKF Smart Lane Switching

intermediate
ArduPilot•2020Varies175h (Medium)

<p>A smarter lane switching mechanism between multiple active lanes based on error integration and innovations.</p>

pythonrosc+++8
Student: ksharshit
Code
Proposal

qaul.net HTTP API

intermediate
freifunk•2019Varies175h (Medium)

<p>Regarding the development of an API for the qaul.net rewrite along with a configuration and message management system.</p>

cluaopenwrt+15
Student: Jess Rogers
Code
Proposal
Showing 2785 - 2808 of 3883 Projects
115116117118119
Proposal
Proposal