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 serves to implement a common framework for applying quantum machine learning algorithms to high energy physics analysis. A major focus will be placed on classifier algorithms that are important for distinguishing signal and background events in high energy physics experiments. The framework will use the quantum variational method as a basic quantum machine learning classifier algorithm.The framework will feature a modular and extensible architecture where its components can be reused to design different machine learning algorithms such as quantum neural networks and a user may contribute to the framework by providing new algorithms and components.</p>
<p>This project aims to implement controller-runtime for Rook nfs-operator and addresses several issues along with it. Currently, Rook nfs-operator only simply watches an event of CustomResource from an informer. Controller-runtime is a good library for building an operator which incorporates the best-practice controller principles.</p>
<p>Community Dictionary (ComDict) is a crowdsourced online dictionary for multiple languages. Each head term in the dictionary is defined only in English and has meaning in multiple languages. Also, each meaning contains examples, definitions, and the voting count. Reactjs and Firebase will be used to develop the system.</p>
<p>This project’s objective is to add an SSH proxy for the Cowrie (<a href="https://www.cowrie.org/" target="_blank">https://www.cowrie.org/</a>) honeypot. Currently, Cowrie emulates an SSH server using Python, and provides proxy functionality only for SSH exec commands, but no interactive terminal sessions. In this project we expect to implement the logic to <strong>forward SSH protocol messages</strong> from clients into backend SSH servers, thus allowing for <strong>full-fledged terminal sessions</strong>, and converting Cowrie into a <strong>high-interaction honeypot</strong>. Our proposal includes the addition of a <strong>backend management module</strong>, which will handle the virtual machines where commands received by the proxy are executed.</p>
<p>Hypervisor (Virtual Machine Monitor) is a software that runs one or more virtual machines. Other than virtualization in cloud, they are also used in Virtual machine introspection to observe the behavior of malware from outside perspective. Traditional hypervisors like xen and kvm has a lot of features that these VMI researchers don’t need. So Bareflank aims to provide all of the scaffolding needed to rapidly prototype new a hypervisors.</p> <p>“LibVMI is a C library that makes it easy to monitor the low-level details of a running virtual machine by viewing its memory, trapping on hardware events, and accessing the vCPU registers”</p> <p>The primary goal of the project is to do Virtual machine introspection using LibVMI in Bareflank hypervisor. This will be achieved in multiple parts.</p> <ul> <li>The first part is to build a hypercall interface and so that both the Libvmi and Bareflank can talk to each other. </li> <li>The second part is to use the interface and do register and memory introspection on both the guest and host virtual machine.</li> <li>create channel for events and add support for Bareflank libvmi events.</li> </ul>
<p>Building an easy all-in-one portal to upload and parse SPDX documents for validation, comparison and conversion and search SPDX license list by forming a Python-Java bridge for integrating various methods from the SPDX JAVA tools library.</p>
<p>Automated creation of kernel configuration files from curated sources, detected hardware, installed packages and user input.</p>
<p>I am willing to devote extra time if required to complete this project. I am much familiar with the TeamMates working flow . And I am always willing to learn new stuff if required.</p>
<p>Orfox, Tor browser for Android, requires a few updates that would help it move from beta to a release.</p> <p>I hope to achieve this this summer!</p> <p>Some of the updates include:</p> <ul> <li>Rebasing</li> <li>Code audits</li> <li>API updates</li> <li>More Orbot integration</li> <li>Tor Button for Orfox</li> </ul>
The OWASP Web Application Honeypot is the only open community project focused on the HTTP application layer, but it currently sits as a dormant proof-of-concept with an outdated logging format, no fingerprint detection, and no path to push threat data into community platforms like MISP. This proposal evolves it into a production-ready, adaptive, and intelligence-grade platform. The solution is built around 8 interconnected deliverables: 1. Versioned JSON logging schema (v1.0) with GeoIP2 and MITRE ATT&CK enrichment 2. Automated CRS version management via nightly GitHub Actions 3. CRS 4.x honeytrap plugin with hot-reload daemon (no container restart required) 4. Shodan Honeyscore-triggered chameleon engine for automatic persona rotation 5. Vulnerable application fingerprint library with 4 personas (Apache, IIS, phpMyAdmin, WordPress) 6. Multi-region AWS deployment framework using Terraform with centralised Kibana 7. MISP and STIX 2.1 threat intelligence exporters with optional TAXII push 8. Industry segment profiles for education, financial, and general deployments switchable via a single environment variable Each deliverable has measurable success criteria and risk mitigation. Built on prior production work in DICOMHawk, GreedyBear, and IntelOwl where identical problems were already solved. Total effort is 350 hours across 13 weeks.
OmegaUp has around 40 MySQL queries that do full table scans making pages slow for students and teachers. The CI pipeline detects them but never fails the build so they go unnoticed. I will optimize these queries by adding indexes and rewriting them in the DAO layer, make CI block new inefficient queries using an allowlist system, and add a performance benchmark to catch slow queries before they reach production. The goal is to make omegaUp faster today and prevent regressions in the future.
Haskell language server (HLS) implements the server part of Language Server Protocol (LSP) to improve user experience of reading and writing Haskell. Signature help is a LSP language feature which shows function signatures and documentation when the cursor is inside a function application. It can also highlight part of the signature related to the current parameter the cursor is at. Users want this useful feature. This project implements signature help for HLS.
This project aims to bring the power of Retrieval-Augmented Generation (RAG) into the Scala ecosystem by building a robust Scala interface to interact with RAG pipelines. I will design a Scala-compatible wrapper to connect with Python-based components like FAISS and Hugging Face Transformers via gRPC or HTTP APIs. The project will also include developing idiomatic Scala modules for preprocessing, querying, and evaluating textual data, making it easier for Scala developers to integrate RAG into NLP or search applications. By providing seamless interoperability and modular architecture, this will empower the Scala community to build intelligent, language-aware systems more efficiently.
TARDIS implements a regression testing framework which is used to compare the current output of TARDIS to a saved data repository to validate code. This data repository is modified at times when there are code/infrastructure changes in TARDIS, this could be environment updates, scientific code changes or more. However, the impact of smaller commits goes unnoticed. There is a comparison notebook implemented that can compare two different commits and spectra in a comprehensive manner but that does not provide a way to compare multiple commits at once. This project aims to build a system to compare the regression data produced by a range of TARDIS commits and will be able to find the commits which impact the regression data files. Also this project aims to enhance TARDIS HDF writing capabilities by adding a HDF writing system to most TARDIS objects and the simulation, so it is easy to reproduce TARDIS objects from stored HDF files.
In today's world sequential recommendation systems are used in various domains-- from life sciences to e-commerce and business. For example, within biology and ecology, recommendation systems help track a species behavior by suggesting research on migration patterns, and within e-commerce these systems are used to better a user's online experience. As such, recommendation systems are vital to systems today and is a important field of research. Despite widespread use, traditional sequential recommendation systems face limitations. They primarily on historical user interactions to predict future preferences however struggle to capture contextual dependencies and adapting to dynamic user behaviors. Similarly, existing models predefined embeddings which restrict the ability to adapt and generalize. As such these problems lead to reduced recommendation accuracy, typically for example in cold-start users. As such, the LLMSeqRec proposal will lead to a more personalized recommendation by interpreting and augmenting sequences with semantic context. Through this, LLMSeqRec can make up for the traditional difficulties-- making more accurate and adaptable recommendations personalized for each user.
COBOL source files may use different encodings. Commonly, these use some 8-bit character encoding like ISO-8859-15 or an EBCDIC one "transferred as binary from the Mainframe". Newer sources are often written in UTF-8, which can pose challenges for user-defined words and literals stored as single-byte characters. The project aims to support files with different encodings and internally convert between UTF-8, UTF-16, stored as byte arrays.
The objective of this project is to convert Writer’s Java UNO API tests to C++. Unit testing is a software testing method by which individual units of source code are tested to determine whether they are fit for use. However, the unit tests for Writer’s UNO API tests are still implemented in Java, making it hard to debug them. LibreOffice has a long term plan to move them to C++. I intend to complete this task as my project for GSoC 2023.
Problem statement: LLDB doesn't support module information in kernel space now. So in my proposal, I want to implement full kernel module support for kernel space. Method: To achieve this goal, I take kgdb as a reference and use the same method in in my project but use lldb as the backend (kld as the frontend). Deliverables: In brief, this project is to implement kernel module supply for lldb which the current lldb doesn't have. After this project, LLDB will support more kernel level debug information and thus facilitate kernel module development.
PolyPhy is an interpretability tool which identifies network structures in both 2 and 3-dimensional data using the novel MCPM algorithm. Users can view and rotate the resulting network. A web app, Polyglot, enables users to navigate a map of the network, hover for detailed views of points, and filter sections of the network based on a novel similarity metric. Despite its excellent interactivity, Polyglot is limited to three precomputed networks. We propose to combine the two tools such that a user can upload any of their own networks from PolyPhy and thus greatly increase the ability of users to interact with their networks from PolyPhy.
C++ 17 and 20 released the par_unseq and unseq execution models which give guarantees to functions which specialize on them that data access functions can be interleaved even between iterations of one thread. This means that these functions are vectorization safe and can thus gain massive boosts in performance by compiler auto-vectorization. Compilers however are conservative and auto-vectorize loops only when they are sure that vectorized versions give the same result as their scalar counterparts and that vectorization will actually end up being profitable. GCC, Clang, MSVC, ICC all rely on different optimization passes in their backend and are all capable of auto-vectorizing certain loop patterns but not all. The goal of this project is to analyze compiler codegen response to different hints and implement a version of the par_unseq and unseq execution policies in HPX that makes use of these guarantees to provide compilers with as many hints as possible to encourage auto-vectorization.
The Arctic sea is a framework for developing OGC services, clients and middleware sharing concepts for encoding and decoding of different formats and encodings, workflows and configuration. It is the backbone for OGC services, clients and middleware. One of the important components of the Arctic Sea framework is Faroe. Faroe is a configuration API currently featuring a JSON and a SQLite backend. It enables the injection and automatic configuration of settings of various types in classes, including a Spring BeanPostprocessor. It allows us to set properties for OGC services. The problem statement thus asks to create a web frontend to create, read, update and delete (CRUD) the JSON settings with a REST API on top of faroe API. I will try to develop a user-friendly UI for the same and make sure CRUD operations are carried out properly through UI, making it extensible and customizable. Also I’ll try to surely implement the optional extension mentioned in the problem statement.
<p>The idea of the project is to extend the coverage of tests in the BrainBox project and also implement Continuous Integration and Continuous Deployment using CircleCI. Currently there are unit, integration and e2e tests written for the BrainBox project but the coverage is not extensive and only amounts up to 16% of the code. Hence the project proposes to extend the coverage of unit and end to end tests, while integrating them in the continuous integration of the platform and implement continuous deployment using CircleCI.</p>
<p>The project focuses on the various high-priority issues to improve Zulip as a project.</p> <p>It includes:</p> <ul> <li>Working on new frontend/backend features or improving existing features.</li> <li>Working on developer tooling area to enhance developer's productivity.</li> <li>Improving black-box test suite (puppeteer tests).</li> <li>Improving codebase.</li> <li>And many small fixes.</li> </ul>
<p>We need to implement new filter/suppression module to to let existing code be as is and validate only new code, which will make introducing Checkstyle to a project easier.</p>