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.
The goal of this project is to update the Python codebase for Appleseed from Python 2 to Python 3 and update the PyQT code and GUI to PyQT6. This update is necessary to ensure that Appleseed continues to function correctly and avoid potential issues that may arise due to Python 2's deprecation. The project will include updating the Boost C++ Libraries to the latest version and ensuring compatibility with other dependencies, including OpenEXR, OIIO, Embree, and Qt. Updating Appleseed to Python 3 may affect some of its dependencies, including Boost, PySide/PyQT, PIL, and other Python dependencies. Overall, this project will help ensure the long-term sustainability of Appleseed by modernizing the codebase and improving the user experience.
String solving is an important feature of symbolic execution for successful security and correctness analysis. In Java Symbolic Pathfinder (SPF), a widely used Java symbolic executor, existing string solving integration lacks support for many string functions, including some frequently used ones. To improve SPF string solving, I will implement support for unhandled string functions based on functions that are already supported. For some functions looping on the input string, I will construct solver constraints by symbolically executing the implementation of those functions. As stretch goals, I also plan to add support to StringBuilder/StringBuffer and implement regex solver integration. The deliverable of this project is an SPF branch with most string functions supported, together with documentation and unit tests for newly supported functions.
<p>Security and Semantic bugs exist in software systems, and discovering them is time-consuming, complicated, and challenging. Several static and dynamic techniques are presented for discovering bugs. However, finding a bug is still a challenging topic. In this work, we investigate developing a prototype tool that uses the benefits of using the lightweight specification, fuzzing, and symbolic execution for discovering security and semantic bugs in an arbitrary Java program. This proposal aims to extend Badger, meaning both SPF and Kelinci, with the ability of handling both pre and postconditions using the runtime assertion checker of OpenJML with the lightweight specification. Also, using and extending <code>Debug.assume()'' and</code>Debug.assert()'' mechanisms in SPF that they work like precondition and postcondition, respectively.</p>
<p>As modern OpenSCAD usage has advanced, it now makes more extensive use of libraries consisting of many files, and the editor features have not kept pace with this more advanced workflow. The goal of this project will be to add different IDE-like features to the integrated text editor thus advancing its usage. This will make the editor more user-friendly and easier to handle large codes. Currently, the editor supports features like syntax highlighting, bracket matching, numbering of lines, besides others. I will work on implementing multi-file editing support to the editor and autocompletion of OpenSCAD keywords.</p>
jpf-core is essentially a JVM that currently fully supports only Java 8. The goal of this project is to make it up-to-date with new features of Java 11. The key feature of Java 11 that is currently not fully supported are bootstrap methods that are generated at load time. They are used for things as common as string concatenation ("Hello, " + name). As of now, many cases are supported, but there are still many programs (and unit tests) that fail with Java 11. The priority of this project is to attain 100% compatibility with Java 11 by fixing the 15 tests failing currently.
The project would undertake the necessary code restructuring to facilitate OpenSCAD's transition to rendering with modern OpenGL. An important early step will be adding clear delineation between code paths that result in underlying calls to the two different rendering methods. This groundwork would then grow into developer-controlled flags that would enable the eventual deprecation of the legacy fixed-function calls. Part of the process will involve assessing the readability and testability of higher-level rendering classes and performing refactoring in line with guidance from other developers. Another key area of focus includes assessing and implementing any remaining workarounds needed to replicate the information exchanged between OpenCSG and the legacy rendering classes.
The project would allow the 3D viewport to support custom shaders for the render mode (F6). This requires retrieving the necessary uniforms and other shader input/outputs, then providing them to the program. Moreover, currently the GUI does not have options to allow the user to manage which shader is used, or add their own. My project would add these interface options to support shader management for the render by the user. Additionally, a set of default shaders could be included which the user could switch between.
<p><strong>An application for users to access biological data extracted from biomedical literature.</strong></p> <p>Project Mentor <strong>Augustin Luna</strong></p> <h3>Objectives</h3> <ul> <li>Easy search capabilities for biomedical entities (e.g., genes, proteins, and chemicals) for a corpus of extracted entities and interactions </li> <li>Users will be able to see the articles that mention entities of interest in easy to interpret manner. </li> <li>Users will be able to view results in a tabulated format </li> <li>Computational users will have access to an API to retrieve results programmatically</li> <li>Use modern technologies for better browser compatibility, user access, and simplified maintenance </li> </ul> <h3>Project Phases</h3> <ol> <li>Planning and deciding our approach towards the project </li> <li>Deciding on data structures</li> <li>Creating schemas and GraphQL interface </li> <li>Generating Wireframes </li> <li>Linking backend and frontend </li> <li>Working on functionalities like search, filter </li> <li>Basic prototype expected to be ready by 23rd June</li> <li>Taking feedback from community and mentors</li> <li>Implementing features advised by community and mentors</li> <li>Deploying the project</li> <li>Working on making a pipeline to automate data addition from <strong>PubMed Central</strong>.</li> </ol>
This project aims to overcome Blender's limitations with spreadsheets and other functionalities. The goal is to have a web interface running alongside Blender. This web interface ideally should be able to show tabular data for objects that Blender knows about, have real-time updates, and execute operators on them. Key tasks for this project include setting up an HTTP web server or a WebSocket connection for communication between the web interface and blender, Sending data from Blender to the web interface, and vice versa, displaying data on the web interface with the ability to execute operators that reflect in Blender, and If time permits, a dynamically generated Gantt Chart for work schedule. Deliverables: 1) Showing tabular data 2) Ability to execute operators 3) Dynamically Generated Gantt Chart
Template Playground is a web-based tool that allows users to create, edit, and test smart legal contract templates. Currently, the application relies on Ant Design for its UI components, which increases bundle size, and limits customization. This project aims to migrate the entire UI from Ant Design to Tailwind CSS, making the platform more lightweight, efficient, and maintainable. Along with the migration, I propose a new layout design. This new design will be introduced to enhance usability, responsiveness, and overall user experience. The goal is to create a modern, intuitive, and visually appealing interface that improves workflow efficiency for users interacting with contract templates.
This initiative focuses first on creating a Rust runtime platform for Concerto. Presently, Concerto's runtime logic resides in JavaScript and we use Node/Browser execution to conduct that logic, however; the logic is becoming more difficult to be reused as expected in other execution environments. The long term plan is to create a reusable Validation Core written in the Rust programming language which loads Concerto entity metamodels in JSON format, validates against the requested Concerto entity types based on the appropriate input metamodel and allows both access to the same validation core as a WASM module which is used from JavaScript executed environments, and also through a native interface for callers that are not executing using vanilla JavaScript.
The goal of this project is to add new functionalities to Newt to be able to create biological maps in GPML format from scratch or edit existing ones. This will provide users to have a web-based alternative to PathVisio where they can easily create/edit GPML maps from any computer with Internet access. The functionalities to be added will also include access to WikiPathways, easy identifier mapping and data visualization etc., as in PathVisio.
The goal of this project is to enhance the usability of Decorator Command Set (DCS) data by developing a utility/method to convert verbose, complex JSON formats into a more human readable YAML representation and back again. Currently, it is highly verbose to read, write, and edit DCS JSON files. The plan is to implement a converter that turns DCS JSON objects into a simple YAML format and back again. The new YAML will be less verbose and more readable, helping people work with DCS better. By the end, a fully integrated converter will be delivered, complete with tests and proper documentation.
This project focuses on improving the Geometry Verification and Validation (V&V) GUI in Qt for the Arbalest application in BRL-CAD. Currently, the prototype GUI provides basic validation output but has several usability limitations such as truncated full-path display, flat result presentation, and limited export options for validation results. These issues make it difficult for users to clearly interpret geometry validation outcomes. In this project, I plan to improve the usability and clarity of the existing V&V GUI by restructuring how validation results are displayed, fixing the full-path column visibility issue, and adding grouped result visualization for easier navigation. I will also implement a downloadable validation report feature that allows users to export results in structured formats such as TXT or JSON, making validation outputs easier to review and share. The expected deliverables include updating the existing V&V GUI implementation to work with the current Arbalest codebase, improving the results panel layout based on a proposed UI mockup, and adding a report generation module integrated into the GUI workflow. These improvements will make the validation interface more practical and user-friendly while keeping the scope aligned with the current prototype architecture.
Gradle is a build automation tool known for its flexibility to build software. A build automation tool is used to automate the creation of applications. The building process includes compiling, linking, and packaging the code. The process becomes more consistent with the help of build automation tools. Currently, SymbolicPathFinder is using Ant as a build automation tool but the Gradle resolves all the issues faced by building tools like Maven and ANT. It is Well-Known to be highly customizable for different projects dealing with various technologies. We can customize the project according to the needs of the project. Gradle is popular for providing high-speed performance, nearly twice as fast as Maven. Gradle makes building common types of projects easy by adding layers of conventions and pre-built functionality through plugins. We can apply all those to enhance our SPF project. At the end of this project, we will get High performance, Build Scan, incremental build (that states it executes the tasks). Some steps to Implement this project : 1. Create Gradle build from scratch. 2. Restructuring of the project. 3. Implement a continuous integration (CI) pipeline. 4. Improve Junit Testing. 5. Update Documentation.
<p>Newt supports the Process Description (PD) and the Activity Flow (AF) graphs of SBGN. However, there is no conversion between these two graphs in the Newt. PD is a detailed version of AF. Thus, from PD, AF can be obtained but not vice versa. There is already a library for converting PD to AF. The goal of this project is to host a service for this converter and then integrate it into Newt.</p>
<p>The goal of this project <strong>‘Diff for Graphs’</strong> is to implement a graph comparison functionality which will allow users to compare two or more graphs that are accessible by them. This includes graphs created by them, graphs shared with them by other users and all the public graphs. This project extends the work done in <strong>‘Git for graphs’</strong> project - which was a part of GSoC ‘18.</p>
Information Delivery Specification (IDS) is a standard for defining information requirements in a computer interpretable form, written in XML. Manually writing XML in compliance with the IDS schema can be an extremely difficult task for non-technical BIM users, giving rise to a need for a web interface to compose IDS specifications in a user-friendly manner. The current implementation suffers from bugs, outdated UI, and lacks important authoring usability features. The primary goal of this proposal is to rebuild the web app on a new foundation - the IfcOpenShell WASM build, eliminating the need for a API backend, improving privacy, and enabling innovative features like in-browser IFC compliance checking, contextual autocompletions, and enhanced UX/UI. The new implementation will be comprised of 3 modules: 1) IDS Module - for composing and editing IDS specifications in a user-friendly way. 2) WASM Module - to interface with IfcOpenShell WASM. 3) Application Module - built with Svelte 5 and shadcn-ui to deliver a modern, responsive UI. Additionally, this proposal introduces a built-in XML (IDS) editor, in-browser audit report generation, and integration with Bonsai’s websocket-based Web UI system for fetching "smart context" from Blender.
This project is primarily focused on creating an interactive display of the carbon cycle forecast and data assimilation system of PEcAn. The main goal is to revive the site-specific R Shiny Forecasting and SDA dashboard that is no longer operational and broaden its scope to cover a larger number of sites. Additionally, the plan is to construct a new comprehensive dashboard that combines both SDA and Forecasting graphs. Moreover, the proposal also aims to establish an automated notification email system for the visualizations.
<p>Implementing following dimensionality reduction techniques and clustering algorithms to clusterMaker2: UMAP, t-SNE, PCA, PCoA, Louvain, Walktrap, Edge Betweenness, Surprise, DBSCAN, Spectral clustering and Self Organizing Map. This project is a continuation from last summer's clusterMaker2 project, when I implemented a feature that allows running the algorithms on a remote server. These algorithms that will be added will also use the remote feature.</p>
<p>The project aims at creating and deploying a user friendly, interactive and accessible website for PEcAN Project. The following objectives will be accomplished after the successful completion of the project.</p> <ul> <li>Revamping the design of the PEcAn Project’s website and drawing wireframes (using figma ).</li> <li>Developing a Static SPA(Single Page Application) website using Docusaurus.</li> <li>Markdown Documentations will be integrated as web pages.</li> <li>Functionality for adding and editing documentation.</li> <li>Setup GitHub actions for continuous integration.</li> <li>Write detailed documentation for users and developers</li> </ul> <p>After accomplishing above tasks we would have a feature-rich, accessible website with a clean and elegant UI.</p>
<p>Ontologies are an integral part of our scientific progress. The ability to share common definitions is crucial to answering questions, thus, an updated and persistent ontology is important to invest in. This project will upgrade the current ontology tagging system of WikiPathways by utilising the recommender REST-API of BioPortal. The first part deals with fixing current data fetching mismatches, where tags are stored and fetched inconsistently. The second part of this project is implementing an intuitive tagging function to the process of creating a pathway, allowing the creator to fetch suggestions from BioPortal and add them with a couple of clicks. Lastly, the final part pertains promoting the quality of the tags by crowdsourcing the votes of visiting users.</p>
The APAP MCP server currently routes every tool call through an internal HTTP loop back to its own Express server, adding unnecessary latency, making MCP handlers impossible to unit test, and discarding all HTTP error context behind generic error strings. The MCP layer has zero automated tests and no client-specific documentation beyond a basic setup guide. This project introduces a shared service layer that both MCP tools and REST routes call directly via Drizzle ORM, eliminating the HTTP round-trip. Structured error types replace generic strings with machine-readable codes and HTTP status preservation. Deliverables: 1. Shared service layer refactor with structured error types across all 8 MCP tool handlers 2. Four-tier test suite (unit, integration, contract, E2E) with 90%+ coverage enforced in GitHub Actions CI 3. Client-specific tutorials for Claude, ChatGPT, and MCP Inspector 4. Developer experience improvements: Docker Compose quickstart, Pino structured logging, /healthz endpoint, and updated CONTRIBUTING.md A working proof-of-concept implementing the core refactor with 53 tests and 98.55% statement coverage is already live at github.com/JayDS22/apap-mcp-poc.
<p>This project intends to make several improvements to compmodelmatch platform which will improve its performance and also add features such as ORCID and OAuth2 API Integration which will result to improve the usability of the platform.</p>