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>I propose to develop an Android App for Science Experiments with PSLab. Due to the growing influence of smartphones, the requirement of an Android counterpart for PSLab is needed. As per the current development status, the device communicates with the app using an OTG Cable using I2C communication. PSLab has an already existing desktop counterpart and the features like oscilloscope, get data of the various sensors on the board etc. and I wish to integrate most of the features in the app along with some better feature suggestions. The project would require initial development of communication libraries followed by implementation of the proposed features and their rigorous testing. An entire development model needs to be developed which would the writing main code, tests to check validity in certain cases, paying attention to the aesthetics/looks of the app etc. The proposed features would require extensive understanding of communication protocols, using APIs in apps, development of tests & making good UI designs. The proposed project has been divided to development & testing phases with time bound schedules for the same.</p>
<p>The inspiration for this proposal is from elements of Minecraft along with some pre-existing suggestions and ideas within Terasology. The concept of Scenarios has been suggested in the past and would be very important in order to properly develop any notion of “static” worlds such as what would exist for Light & Shadow. In addition, it would provide assistance to creation of exploration worlds such as the suggested Maze world.</p> <p>The implementation of scenarios can be thought of as basically creating a “game maker” style engine built into Terasology.</p> <p>As additional smaller, but very important goals attached to this idea, I intend to extend the currently existing tools for creation which mostly include BlockPicker and StructureTemplates both of these tools work well at what they do, but both are still limited for large creations as they require placing everything by hand. This is where the brush tool I propose can come in handy. The brush tool is designed to allow for “brush-strokes” being made using blocks to quickly create large structures and terraforming. These brush tools would allow for the following interactions.</p>
<p>The goal of this project is to extend Apache Airavata to allow in-situ data reporting and analysis for Molecular Dynamics (MD) workflows. The resulting gateway will allow users to create custom event listeners that monitor all simulations and report when a user-defined condition is encountered. It will also allow users to stream partial results and computational resource usage over time. As a proof of concept, the extensions created in this project will be tested using MD trajectory data collected from simulations of a small molecule and standard MD analysis techniques. While this project will be tested using a MD workflow, the result will be extensible to other scientific and big data workflows.</p>
<p>Accelerating the forwarding speed of the LPM principal with poptrie. The goal of this project is to accelerate the forwarding speed of LPM principal with poptrie, a recent data structure that employs a number of features available in modern general-purpose processors to look up the longest prefix lightning fast.</p>
The project focuses on enabling real-time multilingual accessibility for Eventyay’s live streaming platform by introducing interpreter audio alongside existing YouTube video streams. It includes the development of a browser-based interpreter console that captures audio via WebRTC using a Jitsi-based infrastructure, allowing interpreters to stream translated speech with low latency. On the viewer side, a multi-language audio player will allow users to subscribe to preferred language tracks while maintaining synchronization with the video through automatic and user-adjustable timing offsets. On the backend, interpretation settings such as languages, streams, and synchronization offsets will be integrated into the existing Eventyay admin system and associated with sessions. A lightweight audio pipeline will process interpreter input into scalable HLS streams for reliable delivery. Work also includes ensuring seamless integration with the current platform, maintaining synchronization accuracy, and supporting multiple concurrent language streams. The outcome will be a scalable and user-friendly multilingual streaming experience, enabling organizers to configure interpreter settings, interpreters to operate from a unified browser interface, and viewers to seamlessly select their preferred language during live sessions.
The project should deliver an AI-enabled backup camera application for AGL using Fluorite. It captures multiple camera feeds via Gstreamer, stitches them into a top-down bird's-eye view, and a YOLOv8 model for object detection. The model should run on TFLite.
This project aims to further develop an open-source intracranial EEG (iEEG) analysis platform by integrating clinically relevant seizure detection and seizure onset zone (SOZ) estimation algorithms, along with enhanced visualization tools. The goal is to support clinicians and researchers through a semi-automated, transparent, and interactive workflow for epilepsy analysis. By combining automated methods with expert input, the platform will facilitate reproducible and interpretable analyses in both clinical and research settings.
This proposal introduces two new inline tracing capabilities for the Metasploit Framework-KerberosTicketTracePresenter and CertificateTracePresenter designed to provide real-time visibility into authentication artifacts during module execution. Currently Metasploit lacks inline inspection for Kerberos tickets and X.509 certificates, forcing operators to export artifacts or switch tools which disrupts workflow and increases operational risk. This project addresses that limitation by integrating structured presenter-based trace output directly into the msfconsole allowing operators to inspect ticket metadata encryption types timestamps certificate fields and cryptographic fingerprints without leaving the session. The design follows the established Metasploit presenter pattern inspired by HttpTrace and krb5_ccache_presenter ensuring consistency modularity and backward compatibility. Trace output is controlled through granular options off, metadata, full, full_censored, csr allowing flexibility based on operational needs. The implementation includes presenter classes dispatcher integration in the Kerberos client mixin, hooks for AS-REQ, TGS-REQ, AP-REQ, and PKINIT flows, along with RSpec test suites and validation in a local Active Directory lab environment. This work has been refined based on mentor feedback and the design reflects improvements discussed during review. The feature significantly improves operator efficiency debugging capability and OPSEC by eliminating disk-based artifact handling and enabling inline visibility into authentication flows across all Kerberos-enabled modules.
The WebAuthn standard, now widely available on modern Android and iOS devices, enable convenient passwordless authentication satisfying 2FA (biometrics and "have device"). Frequently this involves scanning a QR code followed by unintrusive biometrics such as FaceID on iOS. This project aims to integrate WebAuthn in Rocket.Chat authentication to offer a passwordless, secure login experience. The implementation needs to be aligned with Rocket.Chat’s existing authentication system while ensuring backward compatibility with all existing login methods.
The process of identifying patients meeting certain criteria is crucial to advance research and contributes to new knowledge in medicine and health. So, data on specific populations are necessary to perform such research. However, faced with vast and complex healthcare data, traditional data analysis and processing methods prove to be inadequate.For example, cohort discovery is a popular existing tool that can allow researchers to safely explore the data in the Research Data Warehouse (RDW) prior to making a data request. But in real-world scenarios, the cohort discovery tool is not easy to use because users need to get familiarized with the workflow of the tool and it may even acquire them to write complex query languages, such as SQL. We also observe this inconvenience with the existing cohort discovery tool in D4CG, an open-source organization of the Pediatric Cancer Data Commons. As it works on building communities, platforms and becoming the critical data source for researchers and organizations, it has become evident that implementing an efficient cohort discovery tool would significantly enhance Research and Development (R&D) efficiency. With the rapid growth power of Large Language Models (LLM), this project proposes an innovative solution to enhance the cohort discovery tool by developing a query agent based on LLM to achieve more flexible and efficient data analysis and processing. To prototype this query agent, this project focuses on refining natural language understanding (NLU), improving query accuracy, supporting more complex filters, and integrating feedback mechanisms to learn from user interactions. For example, Given a user question like “Can you help me find patients aged between 20 and 40 who have a history of toothache in the Clinic Table?”, the query agent takes the question along with the corresponding database schema as input. It then generates a query output that satisfies the user’s request.
The aim of this project is to enhance the Beam Yaml API by introducing ML and IO transforms to provide the users with more functionalities. The suggested set of transforms to be implemented are: 1. RunInference 2. ReadFromSpanner 3. WriteToSpanner 4. Enrichment Transforms I also want to add three use cases for the Yaml API, providing end-to-end pipelines demonstrating the use of the newly implemented transforms. The suggested use cases are: 1. Text processing with MLTransform and RunInference 2. Processing tabular data from Spanner 3. Enriching tabular customer data with Enrichment Transform. By expanding the capabilities of the Yaml API, the goal is to streamline the process of constructing and managing data pipelines using Apache Beam. This improvement will enable users to tackle a wider array of data processing tasks with greater ease and efficiency, potentially attracting a broader audience to leverage Apache Beam for their data processing needs.
This proposal outlines a comprehensive plan to implement a system that enables end-users to verify the integrity of their game files against reference checksums. The system will be composed of a server component for storing and comparing checksums and an extension within ScummVM for computing and submitting these checksums.
This proposal targets enhancing the security of OpenPrinting projects, which are foundational to printing software yet vulnerable due to their reliance on C, a language prone to memory safety vulnerabilities. The project aims to integrate these projects with the popular fuzzing framework Google OSS-Fuzz for more conprehensive testing of OpenPrinting projects. This approach not only aims to enhance the testing coverage of exising testing suites but also detect and mitigate vulnerabilities in OpenPrinting projects. This initiative is expected to significantly elevate the security posture of OpenPrinting projects, promoting a more secure open-source ecosystem.
The project aims to enhance the user experience of CircuitVerse organisation by creating a more intuitive and engaging interface suitable for both beginners and experienced users in digital circuit design. Key goals are as follows: integrating UI-based language contribution to enhance language support, improving various aspects of the website's UI, and implementing features like adding dedicated testimonials section, university showcase, and simplified search page. Additionally, the project involves SSO integration, supporting advanced authentication methods, and migrating the UI to Rails view components for improved code efficiency. Overall, the project seeks to elevate CircuitVerse's usability and functionality while maintaining its open and collaborative ethos.
Currently Chromebooks encrypt all user data safely, and they get “erased” by simply erasing the vault containing the encryption key, making the data unreadable. While this is definitely a way to achieve the end goal of making user data unintelligible after the user decided to erase their device, it is not compliant with the current state of the art guidelines on media sanitization defined by NIST. The goal of this project is extending the current method for device safety erase, proposing a way to safely erase data from a Chromebook’s internal storage based on sanitize commands and compliant with the NIST 800-88 Guidelines for media sanitization. This method will also be used during the ChromiumOS powerwashing process.
The Language Server Protocol (LSP) provides a way to write an IDE/editor extension that is compatible with any IDE/editor that supports the LSP. The project aims to address the limitations of the existing JSON Language server in Visual Studio Code (VSCode) by developing a comprehensive JSON Schema Language Server. Leveraging the Language Server Protocol (LSP), this project seeks to develop a Language Server Extension enhancing support for JSON Schema across a variety of platforms. The envisioned solution will fill the gaps in the current VSCode built-in server by introducing essential features such as schema linting, validation, JSON validation against a schema, and JSON linting based on schema. By packaging the language server as a .vsix file, it will be easily distributable and installable, facilitating widespread adoption among developers. Furthermore, the project includes the implementation of a robust automated testing system to ensure the reliability and quality of the language server, complemented by manual testing in both VSCode and Neovim environments to guarantee compatibility and usability.
Many bug reports from almost 10 years ago to even recent times report that GNU Lilypond has been unable to correctly render note subdivision beams and tuple subdivisions, more evidently in some cases of complex rhythm and meter. After comprehensive assessment and analysis of these issues by the developers, the developers have determined that the current code responsible for those capabilities should be rewritten and refactored. The reason that note subdivision and beaming can be difficult to implement is that music theory heavily relies on powers of 2 and their reciprocals. It's very convenient to composers, instrument players and developers too. That convenience doesn't address the problems rhythmic complexity can pose. Concepts such as compound time signatures, tuplets (group of notes that are not bounded by the powers of 2) and manually setting relevant Lilypond attributes. My project proposes a new way of representing the concept of music theory beams and groupings with different object attributes. My project proposes to fix this Lilypond issue by rewriting `lily/beaming-pattern.cc` (the C++ source file mostly responsible for this issue's logic) and fixing/refactoring relevant C++/Scheme source files. I plan to first refactor such source files to fix regular note automatic subdivision and beaming, then fix tuplet subdivision in later weeks. Heavy code modifications will include updating documentation, adding regression tests, and formatting Lilypond's `convert-ly` rules corresponding to the above two issues. Once the issue of beaming subdivisions is fixed, developers and even anyone wishing to compose rhythmically-complex scores should not have to worry about this obstacle.
The minimum constituent parts of an overall Software Bill of Material (SBOM) – referred to as NTIA’s minimum elements – are three broad, interrelated areas (Data Fields, Automation Support, and Practices and Processes). These elements will enable an evolving approach to software transparency, capturing both the technology and the functional operation. The purpose of this project is to check if an SBOM document contains the minimum required data fields such as the supplier name, component name, component version, unique identifiers, dependency relationships, author of the SBOM, and timestamps.
1. Add etcd adapter and redis adapter to improve compatibility 2. Implement the pycasbin-on-cpp to improve performance and add RBAC API to benchmark the casbin(go version) 3. Introduce Django's various components to make pycasbin easier to use
Chromium’s multi-process architecture requires a mechanism for safely communicating between its processes. This requirement is addressed by Mojo - an IPC (inter-process communication) framework that uses the Mojom IDL (interface definition language) to describe interfaces, collections of messages and data structures. The goal of this project is to improve security by introducing a new fuzzing technique - snapshot fuzzing, as an improved alternative to existing fuzzing techniques.
Adding a database abstraction layer for better code maintenance, then using this new layer to add Multi-Tennancy support for the API using data segregation method by creating one database per admin, also adding configuration capabilities to the admins using the new Multi-Tennancy support and finally changing the front-end to be able to use all these new configuration options.
Switching to Conscrypt, simulating the security APIs becomes much more high-fidelity and it achieves the goal of Robolectric to make it similar to an Android environment. Currently, Robolectric uses BouncyCastle as the Java Cryptography Extension (JCE) security provider. Starting in Android P, Android switched to using Google Conscrypt as the security provider. To be more consistent with Android, Robolectric should update the default security provider to Conscrypt. As it is using the BouncyCastle, this means that whenever the JCA APIs are used in a Robolecetric test, BouncyCastle will be used by default. Officially, In Android the default JCE provider is Conscrypt. This is a Java wrapper over BoringSSL. The goal is to have Robolectric switch from BouncyCastle by default to Conscrypt. The Conscrypt module uses BoringSSL, a native library that is a Google fork of OpenSSL and which is used in many Google products like Google Chrome for cryptography and TLS. Conscrypt uses Java code and a native library to provide the Android TLS implementation as well as a large portion of Android cryptographic functionality such as key generators, ciphers, and message digests. Conscrypt is relatively selective and focuses on the most important and widely-used algorithms. Conscrypt also supports the curves in Elliptic Curves crypto operations and it is much faster than BouncyCastle as it is optimized native code. But BoringSSL doesn't have official releases and makes no guarantees around API or ABI stability.
<p>I will be working on adding a new functionality to FURY which shall enable users to visualise various types of proteins via different representations like Richardson aka Ribbon diagrams and molecular surface diagrams. As a part of my stretch goals, I’d like to expand protein representations via other representations including -</p> <ul> <li>Stick</li> <li>Ball and stick</li> <li>Wire</li> <li>Pipes and Planks</li> <li>Sphere</li> </ul>