Explore Projects

<p>Rekognition is an Amazon service capable of identifying objects, text and activities, performing facial analysis and recognition, detecting the frequency of objects or an inappropriate scene, and much more using deep learning. This GSoC proposal aims to build a self-contained module to start off Poor Man’s Rekognition — an open-source version of the commercial service. This initial module, which will be scalable and robust, will have this as the main goal: “Given a set of properly tagged people (suppose for example, a number of celebrities), create an API that can be used to identify such people in other images.” The aim by the end of GSoC is to complete a pipeline that outputs a timeline of scenes in a video, and the different actors in each scene.</p>

Joplin’s end-to-end encryption protects notes during sync, but not on the local device. This project adds local note encryption so users can lock sensitive notes behind a vault password while preserving compatibility with sync and existing E2EE. The implementation will use an option-gated save/load flow, on-demand decryption, protection against plaintext leaks through search and revision history, and a lock screen UI for desktop. Guaranteed deliverables are a working desktop implementation, vault password management, sync/backward-compatibility support, and tests for data-safety and conflict handling. Stretch goals include mobile support, resource encryption, and CLI/Data API integration.

Flood is a torrent monitoring service that works with a variety of clients. The Flood-Mobile app aims to provide a user-friendly mobile interface utilizing the Flood as a backend. My primary goal would be to make the Flood-Mobile app more useful by incorporating the objectives such as RSS Feed feature in the app along with filtering content features, adding notification action support to the app, increasing test coverage of the app, setting up fastlane for easier deployments, improving the file selection architecture and other additional features like adding a quick guide for the app, improving the management of the back button, implementing archive feature in the app and implementing change language feature in the app (multi-language support).

The project aims to enhance VLC by introducing support for WebAssembly (Wasm) plugins, paving the way for a potential replacement of the current Lua scripting functionality in the future. This endeavour involves the development of a Wasm Plugin Manager within VLC, allowing for the utilisation of plugins written in various languages that support Wasm compilation. By introducing this feature, VLC users will have the flexibility to create plugins in their preferred programming languages, streamlining the plugin development process and expanding VLC's capabilities. While the Lua scripting system will remain in place for now, this project lays the groundwork for a potential transition to Wasm-based plugins in the future, offering users even more options for customization and extension of VLC's functionality.

<p>The project aims to add more options to fabric maven plugin for building images for OpenShift build mode. Right now fmp supports two kinds of binary builds namely s2i and docker for OpenShift build mode. The project aims at extending the support for other options such as Buildah and GoogleContainerTools/jib. The projects aims at solving certain aspects such as:-</p> <ol> <li>Separation Of Concerns</li> <li>Daemonless/Security</li> <li>Reproducibility</li> <li>Minimal Images</li> <li>Performance</li> <li>Dockerfile-less</li> <li>Simplifying the build flow</li> </ol> <p>Also there will be unit test cases added for each added feature.</p>

Currently, both of the projects, Talawa-API and Talawa-Admin, provide support for basic functionality related to events (like creation, updation, and deletion of events for an organisation). But this functionality still needs to be completed from a practical point of view. The system lacks some fundamental functionality required for event management (from both the organization's and the attendee's perspective). The purpose of this project includes the following:- 1. Update the API models in a scalable and performant manner to provide support for new event management functionalities that are client agnostic (thus can be consumed on both the Talawa Admin and Talawa Mobile App) 2. Create all the relevant UI for these functionalities in the Talawa Admin. 3. Add a new feedback portal to the Talawa API and Talawa Admin to track the quality of organized events.

VLC's Vulkan video output module is missing two features: HDR tonemapping and subtitle rendering. HDR content played on an SDR monitor appears washed out because no color mapping is applied. The project will be integrating libplacebo tonemapping into Vulkan's fragment shader, so HDR videos can be displayed correctly, by using libplacebo API to generate GLSL code at runtime, compiling it to SPIR-V using shaderc, and injecting it into the fragment shader. Also, currently, subtitles are not rendered at all in the video output module of Vulkan. The project will implement a dedicated Vulkan sub-renderer (similar to the OpenGL one) with alpha-blending enabled to upload the RGBA subtitle regions as textures, to be able to draw them over the video output in their correct positions.

<p>The project primarily focuses on creating a flutter-based native mobile interface for Flood ( <a href="https://flood.js.org" target="_blank">https://flood.js.org</a> ) which is a web interface wrapping over torrent clients like rTorrent, qBittorrent, and Transmission. The main idea is to use the existing API and provide the users with a native mobile experience while still having all the fundamental features and keeping room for plugins (Shoutbox etc) to enhance the feature set with maximum code reusability.</p> <p>Having a native mobile app would also allow the use of platform/device-specific functionality like actionable notifications, snack bar, modal bottom sheet, swipes to delete/archive, etc. which would enhance the user experience.</p>

This proposal outlines several key areas for improvement in the Sample Platform, which is CCExtractor's platform for managing tests, uploading samples, running regression tests, and more. The proposal highlights the need to regularly update code with stable packages for compatibility and security, address bugs and improve functionality such as status reporting to GitHub, implement effective CI/CD, enhance artifact download, and introduce a regression finder feature. The proposal also discusses the importance of Sample Platform in maintaining the stability of CCExtractor and ensuring safe changes in pull requests. To implement these goals, the proposal suggests deprecating support for Python 3.7 and supporting Python 3.10 and 3.11, replacing outdated software, upgrading to Flask 2, and fixing various technical issues with the platform.

Music Blocks v4 has a modular architecture with a block editor, compiler, and execution engine built separately but not yet connected. This project integrates the Masonry visual block editor into the main application, implements block snapping and connection logic so users can build structured programs, and wires the full execution pipeline (blocks to AST to IR to output) so programs produce real music and graphics. Core deliverables: (1) Masonry module integration with palette and workspace (2) snap-based block connections with visual feedback enforcing programming semantics (3) end-to-end execution connecting blocks to the Painter and Singer modules via a real function registry. Stretch goals include inline block editing and workspace zoom/pan/undo.

<p>OWASP-Nettacker currently is a project with less functionality compared to other network penetration testing tools like Nmap, Nessus. In this project, I will be implementing</p> <ol> <li>service and version detection of services running on ports</li> <li>Creating a database of vulnerabilities for Non-Fuzzer based vulnerabilities which can be used to find vulnerabilities by service and version detection to makes the tool less noisy.</li> <li>Adding more data to Vulnerability modules</li> <li>SSL Vulnerabilities</li> <li>Maltego Charts</li> <li>Brute force Modules</li> <li>SPF (Sender Policy Framework) record Testing for mail servers</li> <li>Improving Web UI based on API</li> <li>Implementing nbtscan for information gathering</li> </ol>

This project aims to revamp the Neutralinojs ecosystem to enhance the experience for web developers creating native desktop apps. While the community has developed technology for web-to-native app conversion and offers essential native APIs, there's a significant opportunity to improve the developer experience and platform capabilities. The main objective is to create a package enabling developers to write backend code in their preferred language, supporting multi-language capabilities, and integrating CLI support for seamless backend management. The overhaul includes refining documentation with clear examples and instructions, enhancing templates, and integrating best practices for streamlined development. Additionally, improvements to the CLI interface will provide a user-friendly experience. By addressing these aspects, the project aims to attract more developers, empower existing users, and establish Neutralinojs as a premier platform for converting web apps to native desktop applications.

This proposal focuses on refactoring the current Plugin architecture in the Talawa project to reduce the computation power required to run/host the application. Web sockets will be implemented to make this possible. Current secondary features would be also converted into plugins. The Talawa app would have SPAM mitigation implemented in different aspects like for Sign/login, button debouncing, and SPAM protection in chats. The Additional UI in the admin and mobile app will be added to support “Advertisements” through slideshows, banners or pop-ups to incentivize the community. Local advertisers can purchase ads for a requested period of time by directly contacting the admin of that organization. The process of storing those transactions in a standardized format to support multiple payment providers and the ability to get all payment data at once is also explained. All of these features described above will be tested and converted into plugins to make it controllable by the admins based on whether they want that feature in their organization.

The main objectives of the project idea are to make Talawa offline support robust, Introduce an efficient caching mechanism, and Integrate the chat feature into the mobile application. Currently, Talawa cannot handle offline situations gracefully and does not possess an efficient caching mechanism. To make Talawa offline support robust I will develop an offline actions feature into the application and integrate it with the existing features in the application similar to other social media apps like Instagram & WhatsApp. To back this offline actions feature I will develop an efficient caching mechanism that works in complement with offline actions to cache offline user actions and most frequently accessed data. Aiming to provide the end user with a seamless experience even in inconsistent network situations. I will Integrate the Chat API from Talawa - API into Talawa mobile and ensure the user interface and functionality resemble the most popularly used user-friendly chatting apps.

<p>The aim of this proposal is to enhance user experience. The features which are integrated in this proposal are:-</p> <p>1) <strong>Reply to comments by email -</strong> A feature (much alike github) where a user could reply on a Publiclab note on email. When there is a reply on an email (received to a user at time of publishing or a new comment) thread, a comment will automatically be generated on that particular note on publiclab.org .</p> <p>2) <strong>Daily Digest emails -</strong> In this feature, digest emails would be rolled out to users customised according to their subscribed content. The digest emails would be contain the top few notes with tags subscribed by the user. This feature would require the support of asynchronous job support in the application.</p> <p>3) <strong>A user interface to manage emails regarding subscribed content -</strong> This feature involves forms with various checkboxes to customize emails regarding comments, answers, digests, etc.</p>

<p>OWASP Honeypot : The idea is to: -Test all the modules in the code (currently 4)and if there are bugs found to fix them. -After testing the entire codebase, would remove the duplicated code. -Then I would like to work on packet tracing,currently only the information like IP Address and Country is being extracted from the packets and it's not that useful to classify it as high risk or not.So I would discuss with my mentor as to what all needs to be extracted from the packets and would store in the database.</p> <ul> <li>After that I would like to start with the WEB part of the project,to write new routes and add new visualizations.(this part I am most comfortable with because I already have some industry experience with web) -Then would add new visualizations for the extracted details and also some logic to classify the record in the database as high risk ip because now we would have more information from the packet and not limited to IP Address and country -Also in between testing modules and removing duplicated codes I would work on PR reviews and issues (if there are any raised or found) -Finally at the end would document all the work I did in the wiki section of the project.</li> </ul>

This project adds native PEM keystore support to WildFly Elytron, enabling WildFly to load Kubernetes TLS secrets directly without any manual conversion. Kubernetes exposes TLS certificates and private keys as PEM files, typically as tls.crt and tls.key. Elytron currently requires JKS or PKCS12 keystores, which creates unnecessary friction when deploying applications in containerized environments. This project introduces a new KeyStoreSpi implementation that reads PEM-encoded certificates and private keys from separate files and exposes them as a standard keystore type (PEM). The implementation integrates seamlessly with Elytron’s existing KeyManager and TrustManager infrastructure, allowing it to be used transparently in current configurations. The main deliverables include a robust PEM parser, the PemKeyStoreSpi implementation, support for separate certificate and key files, Elytron configuration integration, comprehensive test coverage, validation using Kubernetes-style TLS secrets, and clear user documentation.

Regolith's Wayland session still depends on GNOME for session startup and settings plumbing. That makes the COSMIC path awkward to install and harder to maintain. I want to build regolith-session-cosmic, an experimental Regolith session that starts through cosmic-session, runs Sway, and removes GNOME from the bootstrap path wherever the packaging and runtime audit shows it can go. The project also includes packaging the required COSMIC components through Regolith's Voulage pipeline so the session can be installed without depending on Pop!_OS repositories, finishing the remaining COSMIC-to-Sway keyboard integration in cosmolith, and validating the core session behavior: display, lock and idle, OSD, and settings persistence. The main deliverables are a bootable experimental COSMIC session for Regolith, packaged COSMIC runtime components with reproducible offline builds for the supported target distros, the remaining input integration work in cosmolith, and a documented validation matrix for the supported session path.

My proposal aims to improve the user experience and developer experience for AsyncAPI-Preview extension. The main problem being solved is the difficulty in identifying and resolving common and custom linting errors in AsyncAPI documents. By leveraging the VSCode API for providing quick/autofixes for linting errors, my proposal plans to add an "Auto Fix" feature for most common and standard Spectral linting errors in AsyncAPI documents. The proposed deliverables for this project include: -Integration of AsyncAPI-Preview and Spectral for VSCode extensions -Implementation of Code Actions for standard Spectral linting errors in AsyncAPI documents -Support for computing json-path to source code and vice versa -Investigation on loading autofix rules from external files to support custom (non-standard) Spectral linting rules Overall, this project aims to streamline the AsyncAPI-Preview process and improve the quality of AsyncAPI documents by providing developers with a more user-friendly and efficient way to identify and fix common and custom linting errors.

FS2, a functional streaming library for Scala, currently utilizes blocking I/O operations, resulting in performance bottlenecks such as context switching and resource contention, particularly in high I/O-bound workloads. To overcome this, the project proposes reimplementing I/O APIs specifically Unix sockets, datagram sockets, and processes by leveraging polling-based mechanisms introduced in Cats Effect v3.6.0, which will remove the reliance on dedicated dispatcher threads and eliminate inefficiencies tied to blocking calls. This reimplementation will support JVM selector-based polling and Native file descriptor polling, while keeping existing implementations as fallbacks for runtimes that do not support the new approach therefore ensuring backward compatibility. The project will deliver these reimplemented APIs alongside comprehensive test suites to verify correctness, performance benchmarks to quantify improvements, and updated API documentation to ensure usability. By improving FS2’s efficiency and scalability, this enhancement will strengthen the Typelevel ecosystem and provide high-performance streaming library tailored for modern applications.

<p>The AeroGear UnifiedPush Server sends native push messages to different mobile operating systems, such as Android, iOS and others. It has already developed good logical structures for sending of push notifications using JMS. Moreover, its "sender" module is mainly constructed of different message queues and their producers and consumers. On the other hand, the server DB is currently based on MySQL/PostgreSQL and each data entry lies in one DB scheme. We need the process for sending of push notifications and the evaluation of message metrics to be as fast as possible and as scalable as possible. Therefore, with an increase of our data problems can be caused by slow writes/reads to DB and not scalable enough message queue usage. The idea of the project is to try to overcome these obstacles and rebuild some modules of the system in the way that they perform well even if the data volume they are operating over increases. For that two different approaches can be taken. To speed up the DB access a new distributed, scalable, big data store HBase can be integrated into the project. For more scalable processing of the data, Apache Kafka can be used instead of JMS.</p>

External subtitles are one of the basic and most used features of VLC. VLC already has functionality to allow auto downloading of subtitles. But sometimes these subtitles go out of sync mainly due to frame rate mismatches between the video and subtitle file, different video versions (e.g., Director's Cut), or technical issues like faulty encoding or laggy streaming. This causes subtitles to be consistently early/late or to gradually drift further off-sync over time. Currently vlc doesn’t have any inbuilt auto sync feature. Due to this users have to manually sync (by setting offset and frame drift) or rely on the external program to sync the subtitle. This project aims to solve this issue by using light VAD (Voice Activity Detection) and the lightest whisper model to match subtitles. The main goal would be to make it as efficient as possible so it can even run on mobile devices. Deliverables: 1. Implement a dummy solution using python. 2. Implement native vlc module to match subtitles. 3. Optimize and test the module on various platforms. 4. Update documentation to reflect project contributions.

The Problem: Sugar currently relies on GTK3, which is nearing end-of-life and doesn’t support Wayland properly. This makes it harder to run on modern Linux systems. The Solution: This project focuses on migrating the core "Fructose" activities (Calculate, Log, Chat, Browse, Read, Terminal, etc.) from GTK3 to GTK4. This isn’t just a direct API update — many parts of the UI depend on older X11-based patterns that need to be reworked. I’ll update layouts to Gtk.Box/Gtk.Grid, move input handling to GTK4 event controllers (like Gtk.GestureClick), and migrate system integrations to newer GTK4-compatible libraries such as WebKitGTK 6.0, VTE 3.91, and Evince 4.0. For more complex rendering (like TurtleArt), I plan to use a Cairo bridge with Gtk.Snapshot.append_cairo() instead of rewriting everything from scratch. Deliverables: A working GTK4 port of the supported Fructose activities that runs properly on Wayland. Since the Sugar shell is still evolving, I’ll validate everything locally using my standalone main.py wrapper before integration.