Explore Projects

<p><a href="https://knative.dev/" target="_blank">Knative</a> is an open-source community project that extends Kubernetes with modules for deploying, operating, and maintaining serverless, cloud-native applications. The serverless cloud computing model has the potential to improve developer efficiency while decreasing operating costs.The project idea is to develop Charmil, an open-source Golang-based platform that will serve as a package manager which assists in the discovery and installation of plugins from a community-curated plugin index. These plugins can then be embedded into any host CLI with additional features such as new version detection and smooth upgrades.Through Charmil, each CLI will be able to install other CLIs as extensions, thereby organizing them in a hierarchy. This functionality of Charmil will later be used to add new features on top of the Knative CLI.</p>

Kolibri offers a well integrated EPUB renderer for its users with smooth responsiveness, control over the text size, and six color themes to choose from. The existing color themes include variations for both light and dark modes. However, those color themes are fixed to the application and cannot be fine tuned as per individual user needs. Objective of this project is to design and implement a custom color picker component for the Kolibri EPUB renderer so that users can have their own custom color themes in the application. Deliverables of the project: 1. Section in UI to display custom themes 2. Integrated color picker to create and modify custom themes 3. Functionalities of adding, editing, removing custom themes and apply them into EPUB renderer Tools to be used: 1. epub.js library 2. Alwan color picker

BugSim (Bug Simulator and Learning) is an advanced bug simulation platform integrated into OWASP BLT. It helps security researchers, ethical hackers, and developers understand, simulate, and resolve vulnerabilities in real-world environments. The project includes features like: Hands-on bug simulation and learning with various vulnerability categories (SQL Injection, XSS, CSRF, etc.). Weekly vulnerability challenges and structured bug reporting. Integration with OWASP ZAP for automated security testing. Live hackathons and competitive bug hunting with leaderboards. Gamification with points, badges, and rewards. This project will enhance OWASP BLT by creating an engaging and interactive cybersecurity learning platform. The deliverables include a fully functional BugSim module, complete with vulnerability simulations, a scoring system, and real-time security reporting.

<p>WildFly Elytron is a new security framework developed by WildFly to provide a single unified security framework across whole of the application server which replaced the pre existing Java Authentication and Authorization Service (JAAS) which used to be the standard Pluggable Authentication Module (PAM) information security framework. To extend Elytron’s functionality beyond the existing security realms, custom security realms can be implemented using existing Elytron’s APIs and SPIs for their usage in WildFly Elytron subsystem. Now to extend this functionality of custom development to scripting languages other than Java, Java ScriptEngine is used. During the summer as the project of GSoC under JBoss Community, I’ll be working on extending the functionality of WildFly Elytron’s implementation of custom security realms using other scripting languages.</p>

<p>The​ support for Python 2 will be dropped in the coming years and thus it is important to switch to Python 3. There is a need to make sugar-toolkit and activities compatible with Python 3, to ensure the smooth functioning of the sugar activities in the future. The aim of this project is to boost this necessity.</p> <h5>Target</h5> <p>Following are the targets of this project:-</p> <ul> <li>To port all static telepathy bindings to TelepathyGLib.</li> <li>Make activity-chooser window modal.</li> <li>Make sugar-toolkit compatible with both Python 2 and Python 3.</li> <li>Make sugar-desktop compatible with Python 3.</li> <li>Port sugar-activities to Python 3 and make a release.</li> <li>Write the necessary documentation.</li> </ul>

Taskwarrior is a free and open source software that manages your to-do list from the command line. It lets you keep your to-do locally but there’s also server support so you can sync between different computers, you can build scripts around it (since it’s command line based), it has a powerful filtering system, etc. Currently, the users have to use third party services in order to sync the Taskwarrior app with their Taskwarrior client. If the third-party service experiences downtime or discontinuation of service, it can disrupt the syncing functionality of the app, leading to a bad user experience. This project aims to develop a comprehensive platform, named CCSync that can be used to sync tasks with the taskserver. Thus, this proposal is about building a service for the app, that would help in syncing perfectly between various platforms, and removing the friction of exploring, signing up and relying on different third party services.

CCExtractor’s v1.00 release requires confidence across every part of the project. Currently, test results in CCExtractor are not fully reliable — tests break or appear to be fixed by PRs that do not even touch the relevant code, making it difficult to confidently assess regressions and overall stability. This proposal focuses on strengthening the testing infrastructure as a whole and making it reliable again, fixing regressions that lead to incorrect outcomes, expanding test coverage to parts of the codebase that are not properly verified today, syncing the Flutter GUI with the CLI so all supported features are accessible, and stabilizing the release process so v1.00 ships cleanly across platforms. As this project gets completed, CCExtractor will be ready for its v1.00 release, with CI passing, parts of the codebase that are currently untested covered, an up-to-date CCExtractor GUI, and a streamlined release and development workflow.

<p>Until now, the traditional ways to navigate across a web browser are by using a mouse or a keyboard. Browser navigation was not much extended as an application of other devices such as game controllers that can be made compatible with the browser through the use of APIs.</p> <p>Gamepads are very popular devices, and a lot of work has been done to extend its usefulness to a wide range of people, such as the <strong>one-handed controllers</strong>, which are designed for people with limited mobility or amputees.</p> <p>The idea behind the project is to develop a solution that makes it possible to navigate across the browser using a game controller. This project would establish game controllers as an alternative to a keyboard and a mouse, by providing the users with a means to use their game controllers to surf across the webpages and the web browser.</p> <p>The project will be an external aid to the websites and web applications that do not themselves provide gamepad support.</p>

<p>Talawa is an open source project helping people with same interest to collaborate together. It deals with managing the members of the group via help of Talawa admin panal. Tawala appilcation helps members to join organizations of their interest via organization's Tawala-api hosted URL.</p> <h4>Talawa Feature:</h4> <ul> <li>[x] International language support.</li> <li>[x] Theming</li> <li>[x] Messaging</li> <li>[x] Organization joining</li> <li>[x] Organization switching on same server, feeds, event creation/registration.</li> <li>[x] Notifications</li> <li>[x] Verified account creation</li> <li>[x] Account password recovery</li> <li>[x] Signup from google and facebook</li> <li>[x] Responsive Layout</li> </ul>

<p>With the introduction of the Web Audio API and music frameworks such as Flocking, it's possible to make music and develop custom instruments entirely using Web technologies.</p> <p>A variety of user interface component libraries, such as Nexus UI, jQuery Kontrol, Interface.js and G200K's Polymer controls, have been developed to assist in the creation of musical interfaces. However, the majority of them aren't very "web-like." Many are based on Canvas or bitmap images, and aren't compatible with responsive design techniques, can't be easily re-styled or customized using tools like CSS, and aren't accessible via the keyboard or with assistive technologies such as a screenreader.</p> <p>This project will involve the creation of a small collection of high-quality, responsive, SVG or DOM-based musical user interface controls such as knobs, sliders, x/y pads, button matrices, envelope editors, waveform viewers.</p>

Kolibri's QTI 3.0 viewer currently renders only Multiple Choice and Text Entry, leaving the majority of the specification's interaction types unsupported. This project extends the plugin to implement six additional types: Inline Choice, Match, Order, True/False, Gap Match, and Fill-in-the-Blank — each requiring careful integration with the existing SafeHTML rendering registry and QTIVariable response system. The core technical challenges are accessibility and interaction fidelity: drag-and-drop interactions (Order and Gap Match) require a fully keyboard-native select-to-place model as the primary interaction, with SortableJS-based drag as the pointer enhancement. Match Interaction requires a directed-pair association model rendered as an accessible grid. All six types must support RTL languages, touch devices, and low-end hardware — not as retrofits, but as first-class constraints from the start.

<p>Sugar Labs has more than 250 activities GitHub and elsewhere which have scope for improvement. Since the support for Python2 was withdrawn from Python Foundation, porting the activities to Python3 and GTK+ 3 is very crucial. My work on this project includes,</p> <ul> <li>Porting activities to <strong>GTK+ 3</strong> and <strong>Python3</strong>.</li> <li>Implementing <strong>basic game design features</strong> which attracts the children (activities from <em>Honey</em>).</li> <li>Implementing <strong>original design features</strong> (activities from <em>Fructose</em> ).</li> <li>Adding <strong>activity specific features</strong> to enhance <em>User Interface</em> and <em>User Experience</em> .</li> <li><strong>Testing and modifying</strong> the activities to ensure at least <em>15 activities are read to release</em>.</li> </ul>

The fw-fanctrl tool currently relies on calling the ectool CLI repeatedly to control and monitor fan behavior on Framework laptops. This approach introduces performance overhead due to frequent subprocess creation and text parsing. The goal of this project is to improve efficiency and maintainability by converting ectool into a shared library and integrating it directly with fw-fanctrl using Python bindings. I have already implemented a working prototype using ctypes, exposing essential EC functions as shared library calls. During GSoC, I will refine and extend this prototype and expand the shared library to support more ectool functionalities. I will also benchmark and optimize both ectool and fw-fanctrl, and contribute to building a simple cross-platform GUI. Deliverables include: • Full ectool library interface • Ectool optimizations • Python bindings and integration with fw-fanctrl • Fw-fanctrl optimizations • fw-fanctrl GUI contribution

<p>The scope of this project is to improve the BookReader framework in two ways.:</p> <ul> <li>The first one is implementing a series of comprehensive end to end tests for the framework. These tests will be made using JS-based test applications which will be chosen based on a written evaluation of the capabilities and functionalities.</li> <li>The second part consists in improving BookReader in order to make the framework more easily implementable outside archive.org. Currently BookReader is very book-centered, but it may find uses for other sources such as newspapers and magazines. The current number of easy-to-change parameters available in the BookReader demos and templates is quite small, and doesn’t allow great customization. This part of the project consists in improving and expanding the parameter system (included in the E2E testing). This allows for a more widespread use of the framework even for not-so-expert users and for other sources such as newspapers and magazines.</li> </ul>

JavaScript lacks a general purpose and cache efficient multi-dimensional array API for operating on large datasets of high-dimensionality. To address this limitation, stdlib provides ndarray API for creating and manipulating multi-dimensional arrays. This project aims to extend those efforts by achieving full API parity between stdlib ndarrays and built-in JavaScript arrays. This work will include implementing functions such as concat, find, flat, includes, indexOf, reduce, some, none, any, with, sort and others to facilitate high-performance data transformation and manipulation. For performance intensive operations such as searching, sorting and reductions, this project will develop C implementations and corresponding Node.js native add-ons for accelerated performance. These enhancements will allow JavaScript developers to work with multi-dimensional arrays with the same ease as working with built-in arrays and thus expand JavaScript's capabilities for scientific and numerical computing.

The goal of this project is to develop JavaScript implementations of LAPACK (Linear Algebra Package) routines. Each implementation will provide both a strided API and an ndarray API to ensure compatibility with stdlib ndarrays, while supporting both row-major (C-style) and column-major (Fortran-style) storage layouts, overcoming the original LAPACK's column-major limitation. The project covers both lower level helper routines and higher level user facing routines. To further optimize these routines, techniques such as loop reordering and loop tiling will be used. The project will include a comprehensive test suite to achieve 100% test coverage and thorough benchmarks to validate performance. All functionality will be well-documented using Markdown and JSDoc to provide clear usage instructions and technical details. Upon the completion of this project, users will be able to call LAPACK routines in JavaScript environments, including web browsers.

<p><strong>Problem:</strong> Many users use Joplin for research purposes, so it is natural for them to do citations all the time. Accordingly, adding a feature that supports citations and BibTeX will be of great benefit to Joplin.</p> <p><strong>Solution</strong>: The solution can be described as a plugin that can do the following:</p> <ul> <li>Read from a source of citations (a <code>.bib</code> file).</li> <li>Allow the user to choose from a list of previously imported citations.</li> <li>Insert references into the note content.</li> </ul> <p>There are other requirements that must be met. For example, the UI should be as user-friendly as possible, automated and manual tests are to be carried out, every component of the codebase will have a documentation.</p> <p><strong>Implementation:</strong> The implementation relys heavily on Joplin's plugin API to do all sorts of things such as showing dialogs, accessing settings, and modifying content.</p>

<p>This project aims to develop a novel method of automatically synchronizing the lyrics of a song to its corresponding audio, i.e. a line from the lyrics is displayed at the corresponding moment in the song in which that line is sung. The primary method through which this synchronization will be done is through syllabic analysis. Applications exist where the number of syllables spoken in an audio file can be extracted without processing the words themselves, resulting in much faster runtimes. By similarly analyzing the number of syllables in a chunk of text, a process for which several very good algorithms exist, we can roughly match the timestamp of each syllable in the audio file to the corresponding syllable in the lyrical text. This process would take place in a separate module than the actual SwagLyric application so as to facilitate speed of retrieval when the user is actually streaming. Several obstacles, which will be discussed in more detail, exist: these include stripping away background music and getting specific audio information from Spotify’s stream.</p>

<p>My project mainly deals with all the small but essential enhancements which are stated in the GitHub issues section. These are what I have experienced as well.<br> The issue is that a lot of the vulnerability testing modules have not been updated for a long time and have stopped working. The project has become unstable due to the lesser number of contributions.<br> Hence, I want to help stabilize the project and add a few much-needed features.</p> <p>In order to achieve the same, I would be working on:</p> <ul> <li>Adding the custom Test groups feature to the system.</li> <li>Fixing the framework freezing issue which happens due to the synchronous connection with the database.</li> <li>Implementing a celery worker for remote plugin processing </li> <li>Upgrading or replacing deprecated tools with suitable alternatives.</li> <li>Migrating from Travis CI to GitHub actions</li> <li>Updating the Python code.</li> <li>Documenting the Changes.</li> </ul>

<p>Drools and Java can work together. Java and Minecraft work together. The obvious next step is to get Drools and Minecraft to work together.</p> <p>The plan is as follows:</p> <p>--A Minecraft mod boots up a list of Drools rules. These are either stored in a predetermined directory, or listed in a config file.</p> <p>--Minecraft does it's start-up routines. The user loads a world.</p> <p>--Each tick (world update) (or X ticks, determined by efficiency needs), the mod executes the rules.</p> <p>--The rules call functions in the mod's Drools API. This is where the majority of the work will come in—I'll have to write a largish set of functions for drools to use. The functions will take two shapes: returning boolean values for tests, or acting upon the world.</p> <p>--The mod reacts to the function calls, altering the world...</p> <p>–...which the user then interacts with.</p>

rTorrent is a stable, high-performance and low resource consumption BitTorrent client. This GSoC project will replace the antique SCGI protocol with Websocket, which will allows real-time events, less serialization/transfer overheads, better security, etc. We will introduce uWebsockets into the rTorrent to make client can communicate with rTorrent via websocket protocol, client can subscribe some specific topics, once the event occurs, server will push the notification to client automatically; implement some callback function and bind to the events we care about, execute them when event occurs. For secuity and convenient reason, we will implement websockets over unix domain socket, which could be access restricted as a file, much efficient and safe than a TCP:IP port. There isn't a modern c++ websockets library that supports unix domain socket, we will add this important feature into uWebsockets, possibly by PR to office repo (if it will be accept) or personal fork.

This project enhances OpenCRE’s cybersecurity compliance platform by addressing scalability, usability, and transparency gaps. The resource-intensive gap analysis tool will be optimized through Neo4j query refinements, Redis caching, and Python code streamlining to run efficiently on laptops (under 5 hours, <16GB RAM). A React-based frontend for MyOpenCRE will simplify compliance workflows with drag-and-drop CSV uploads and AI automation (leveraging NLP models) to map standards like SOC2 to CREs, while unmapped controls trigger suggestions for new CREs. The Explorer module gains debugging tools to visualize hierarchical relationships, root nodes, and metadata (e.g., shared tags), improving maintainability. Deliverables include a performant engine, intuitive UI, rigorous testing (50%+ coverage), and documentation, all merged into OpenCRE’s codebase to empower enterprises, auditors, and contributors with scalable, open-source compliance management.

The current OWASP Snapshot system is passive and requires manual updates, forcing community members to constantly check the website to see what has changed across the organization. This project solves that problem by transforming snapshots into an active, automated digest platform. I will build a system that automatically collects weekly updates expanding the scope to include events, blog posts, and pull requests and delivers them directly to interested users. Contributors will be able to customize their subscriptions, choosing exactly which projects and data types they want to follow. I will also redesign the website's snapshot pages to support date-range filtering, full content display, and social sharing. The core architecture will prioritize GraphQL for all frontend needs. The primary deliverables are the automated processing pipeline, the personalized email newsletter system, subscription management, and the enhanced web interface. A snapshot feedback system and supplementary REST endpoints are planned as stretch goals.