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.
Currently, in OpenYurt, the core component YurtHub—which acts as a transparent proxy between edge node system components (e.g., kubelet, CNI, CoreDNS, kube-proxy) and the Kubernetes API server—is deployed as a systemd service on each edge node. The installation is performed exclusively via the community-provided tool YurtAdm during node joining. This approach imposes a significant limitation: users must use YurtAdm to onboard nodes, making it impossible to install YurtHub on existing Kubernetes nodes that were not initially provisioned with YurtAdm. To improve flexibility and user experience, the community aims to support a label-driven, declarative installation mechanism: 1. When a specific label (e.g., openyurt.io/is-edge-worker=true) is added to a node, YurtHub should be automatically installed and started on that node. 2. Conversely, when the label is removed, YurtHub should be gracefully uninstalled and its resources cleaned up. This enhancement will enable seamless integration of OpenYurt into existing Kubernetes clusters without requiring re-onboarding of nodes. Expected Outcome: 1. Design and implement a controller/operator that watches for node labels and triggers YurtHub lifecycle operations. 2. Develop an installation/uninstallation mechanism that: a. Installs YurtHub as a systemd service. b. Ensures idempotency and handles failures gracefully. c. Cleans up all YurtHub-related files, configurations, and services
<p>Improve the performance and scalability of TEAMMATES.</p> <ol> <li>Migrate Storage component to Objectify API<ul> <li>Rewrite entire Storage layer to use Objectify instead of JDO</li> <li>Deploy change and divert small amount of live traffic to new version for testing</li> <li>Turn on Objectify global cache (uses memcached); do similar isolated testing</li> <li>Fix issues surfaced during live testing (if any), then fully deploy new version</li> </ul> </li> <li>Write performance profiling tests for Storage and Logic components<ul> <li>All methods in Storage and Logic API to be profiled for cost and performance</li> <li>Use remote API client for client-driven testing</li> <li>Use task queues for app-driven testing</li> <li>Results to be used as a benchmark when making changes to the architecture</li> </ul> </li> <li>Redesign schema<ul> <li>Determine entity groups based on GAE transaction limits and our usage</li> <li>Use conceptual relationships as much as possible while keeping within limits</li> <li>Plan for extensibility: should be able to support new features like LTI compliance without too much effort</li> </ul> </li> </ol>
ImageLab is a block-based image processing tool built with Blockly and OpenCV . It helps students learn image processing by building pipelines with visual blocks. Problem statement: This project has the following key issues: This project will implement "Interactive Learning Mode" transforming ImageLab into a transparent, collaborative, and scalable learning ecosystem. First, per-step processing that returns intermediate image outputs after every operator, displayed in a scrollable filmstrip timeline so students can see the output after each step and what each step is contributing for the final output. Second, an image analysis panel showing RGB histograms and metadata for any selected step. Third, pipeline persistence allowing students to save, load, version, and share pipelines using secure share tokens. Fourth, a batch processing engine to run one pipeline across multiple images concurrently with progress tracking and ZIP download. Fifth, custom composite operators (macros) that let students save reusable block sub-chains into the Blockly toolbox. Deliverables: A production-ready fully tested interactive step viewer, image analysis panel with Canvas-based histogram renderer, SQLModel backed pipeline persistence with HMAC share tokens, asyncio batch processing engine, and a macro system with DAG validation and Blockly toolbox injection.
Bio-Block is an open-source healthcare data marketplace on Ethereum and IPFS that handles the full upload → anonymize → encrypt → sell → download lifecycle. However, the pipeline stops at download — once a buyer purchases and decrypts a dataset, there is no way to analyze it inside Bio-Block. This project adds a data analytics layer by introducing a dedicated FastAPI Analytics API (port 3003), a lightweight AnalyticsRegistry smart contract for on-chain result tracking, and a React dashboard for visualizations. The system supports three levels of analysis: graphical (distribution plots, heatmaps, scatter plots via matplotlib/plotly), descriptive (summary statistics, correlation matrices via pandas), and inferential (t-tests, chi-square, ANOVA via scipy/statsmodels). Results are stored on IPFS and linked to their source datasets on-chain via the AnalyticsRegistry contract, maintaining an unbroken chain of custody from data purchase through analysis. Deliverables include: (1) Analytics API microservice with EIP-712 authentication, (2) AnalyticsRegistry.sol smart contract deployed on Sepolia, (3) IPFS result storage and on-chain attestation pipeline, (4) Interactive React analytics dashboard integrated into the existing frontend, (5) Comprehensive test suite (80%+ coverage) and documentation. An optional differential privacy layer using OpenDP is planned as a stretch goal.
<p>Open Event Organizer is an Android Application for Event Organizers and Entry Managers. It is a client side application for another project under FOSSASIA named Open Event Organizer Server.</p> <p>The core features implemented in the app are:</p> <ul> <li>Scan a QR code to validate an attendee's check-in</li> <li>Overview of Sales</li> <li>Ticket Management</li> <li>Edit Basic Event Details</li> <li>Offline Support to the above-mentioned features</li> </ul> <p>The app is designed on the Model View Presenter Architecture which enables robust unit testing. Each feature implemented in the app has a complete coverage of unit tests. The app uses most of the modern open source technologies like ReactiveX API for multithreading, Dagger for dependency injection, OkHttp+Retrofit for handling network requests, Evernote's android-job for handling jobs in the background, JSON API-converter to handle JSON API schema responses, Google Vision API for scanning QR code, Glide for image loading/caching, Jackson to parse JSON data, Leakcanary to detect memory leaks, Lombok for logs, Mockito Framework for unit tests, DbFlow ORM database library, Data Binding etc. Material Design Guideline is followed for the UI in the app.</p>
The healthcare system in Pakistan, particularly in rural areas, faces significant challenges due to limited access to medical facilities and high costs of conventional diagnostic equipment. These constraints leave a large portion of the population underserved, with limited access to timely and reliable healthcare. This project aims to address these gaps by providing a low-cost, portable healthcare solution powered by energy-efficient Edge-AI. By leveraging advancements in RISC-V technology, the proposed solution can revolutionize healthcare delivery in underprivileged areas, ensuring affordable and accessible diagnostics for all. The project, Healthcare-Centric Edge-AI Development on RVMCU Architecture, builds upon the RVMCU, a RISC-V microcontroller designed during the Linux Foundation's Spring 2024 LFX Mentorship Program. The RVMCU, which is compliant with the RV32IMC_Zba_Zbb_Zicsr_Zifencei specifications, was developed as an ultra-low-power, versatile SoC. This proposal seeks to extend that foundational work to enable healthcare-centric applications, specifically targeting wearable and portable devices. The enhanced RVMCU architecture will support diverse healthcare sensors (e.g., cough monitors, heartbeat detectors, ECG sensors) and provide real-time AI-powered analytics. The emphasis will be on achieving energy efficiency, modularity in hardware and firmware design, and seamless integration with AI frameworks optimized for edge computing.
I work on Gitcord, a tool that connects a GitHub organization with a Discord server to help track and manage open-source contributions. The system will collect GitHub events such as issues, pull requests, reviews, and merges, store them locally, and calculate contributor scores based on configurable rules. The automation will follow a simple pipeline (Read → Plan → Report → Apply) so that every action can be reviewed before it is applied. To keep the system safe, it will run in dry-run mode by default and generate audit reports for maintainers. The project will also include a Discord bot that allows contributors to interact with the system directly from Discord. Contributors will link their GitHub and Discord accounts using a verification step instead of OAuth. Through bot commands, users will be able to check contribution summaries, view pull request information, request issues, and receive notifications about reviews, assignments, and merged pull requests. Gitcord will follow a local-first approach, storing data in a SQLite database rather than relying on external services. It will maintain records such as contribution history, identity mappings, audit logs, and notification history. The project will also include documentation, YAML-based configuration, Docker support, and automated tests so that organizations can deploy and maintain the system more easily.
HPX already has partial Tracy support and stronger integrations with tools like VTune and APEX, but tracing is still fragmented and largely thread-centric. This makes it difficult to understand how tasks actually behave, especially across suspension, resumption, and asynchronous dependencies. This project focuses on strengthening and extending Tracy integration in HPX by building on the existing hpx::tracing abstraction and expanding task-level instrumentation across key runtime paths. The goal is to make task execution easier to follow by improving lifecycle visibility, especially around suspend/resume behavior, and by adding initial causal signals (for example, future fulfillment and other synchronization events) to help explain why tasks resume. The work will also extend tracing to execution paths that currently lack visibility, such as fork_join_executor and continuation execution, and introduce scalable controls like filtering and sampling to keep tracing usable in fine-grained workloads. As a stretch goal, I will explore optional trace-context propagation across parcel paths to enable cross-locality correlation in distributed runs. The expected deliverables include integrated tracing hooks across core runtime components, improved suspend/resume tracing, better coverage of executor and continuation paths, benchmark-validated low-overhead operation, and clear documentation for both maintainers and users.
<p>loklak_depot is a new product, which aims to be a platform, for all things data. The big-picture aim is to:</p> <ol> <li>using the data loklak scrapes from Twitter, and use / scrape data from other sources.</li> <li>Generate a system working on NLP which accept input regarding the above data in Natural Language, and display it. This system, named AskSusi, is proficient of doing stuff that Google Search does, in addition it displays more results from data scraped from other websites. It will also be integrated as a bot on Slack, Messenger etc.</li> <li>Integrate third-party applications like WooCommerce, and create on-sale crawlers (like DiffBot), and enable customers to utilise those data dumps.</li> <li>Create an accounts system to enable authenticated clients (using AAA provisioning) to access the NLP system, the loklak apps including third-party, and also enable them to use APIs which aren't directly accessible on loklak (<a href="http://loklak.org/api.html" target="_blank">yellow and red level accessibility</a>). </li> <li>Add IoT support and website plugins.</li> </ol> <p>My work will focus on developing the main loklak_depot functionality, specifically work on the Secure Accounts and AAA system, on developing AskSusi and make them use the data scraped, and fix server issues in general.</p>
This proposal aims to implement HTTP/3 communication for Dubbo Triple in the Go language environment, enhancing the connection management capabilities of the Triple protocol in dubbo-go. The proposal will address the compatibility issues between Triple communication in dubbo-go and dubbo-java by implementing keep-alive functionality at the Triple protocol layer. Additionally, the proposal plans to organize and standardize the error codes of the Triple protocol and output necessary log information. By developing a Triple HTTP/3 server and client, seamless and high-performance communication between Dubbo Java and Dubbo Go over the HTTP/3 protocol will be achieved. We will design a connection pool to effectively manage Triple connections and ensure the validity of connections through a PING-PONG mechanism between the server and client, thus realizing keep-alive functionality. Furthermore, the error codes of the Triple protocol will be standardized according to Dubbo Java's standards to facilitate developers in obtaining detailed log information during the debugging process. The final deliverable of the proposal is to achieve high-performance, barrier-free communication between Dubbo Go and Dubbo Java through the Triple protocol, ensuring perfect compatibility and support for interaction via the HTTP/3 protocol. Users will be able to enjoy flexible keep-alive functionality and improve debugging efficiency through standardized error codes.
This proposal aims to implement intelligent event classification, natural language search, and EXIF metadata read-write capabilities for image metadata portability. Key backend upgrades include implementing image metadata based image clustering with SigLIP2 for visual similarity-driven clustering. It introduces application optimization techniques like modular AI model management, allowing users to extend functionality on demand without bloating the base install, to keep the core application lightweight. It improves face clustering accuracy by addressing confirmed gaps in the current DBSCAN pipeline, including adaptive eps estimation and a face quality gate. On the frontend side, a new Memories UI will be introduced with advanced sorting features, user notifications, video support, along with a new landing page for the product launch. A major addition is shareable album links: users will be able to generate secure, token-based links to share selected photos over the network while the PictoPy backend is running, with new API endpoints serving image data directly to a lightweight web-based receiver. Additionally, comprehensive documentation—including contributing guides, API references, and setup videos—will encourage new developers to contribute. These improvements will make PictoPy more user-friendly, scalable, and ready for widespread adoption.
<p>Systems biology researchers study the network of molecular interactions within a biological system and publish the deduced models in a diagram format. Many XML variants were developed to represent diagrams, including SBML and SBGN. However, SBML can represent much more complex models than SBGN. For example, the SBML qual extension package can mechanistically describe events in its models, such as the relationship that A activates C, B activates C, but A and B cannot activate C at the same time. The SBGN Activity Flow language can describe a similar relationship, but the relationship is represented visually only, and therefore is not stored in its model. The incompatibilities between SBML and SBGN prevent direct comparison between the models.</p> <p>In this project, I will build tools to support bidirectional conversion between SBML and SBGN, which acts as a machinery to map between SBGN-specific and SBML-specific information. SBML Layout package will be used to represent SBML diagrams, and the SBML qual package used to store the logic model.</p> <p>Blog: <a href="http://haleyyew-gsoc.blogspot.ca/" target="_blank">http://haleyyew-gsoc.blogspot.ca/</a></p> <p>Repository: <a href="https://github.com/NRNB-GSoC2017-SBML2SBGNML-Converters/SBML2SBGNML" target="_blank">https://github.com/NRNB-GSoC2017-SBML2SBGNML-Converters/SBML2SBGNML</a></p>
Mesa-Geo currently suffers from three structural problems that make it impractical at realistic geographic scale: a memory bottleneck from instantiating one Python object per raster pixel, a fractured coordinate system that silently conflates three incompatible reference frames, and a broken Cell/Agent abstraction that floods the agent registry with millions of ephemeral entries. This project resolves all three problems through four focused changes: refactoring RasterLayer onto a PropertyLayer NumPy backend, decoupling Cell from mesa.Agent through a weakref identity cache, delivering a RasterCellCollection aggregation API with scipy.ndimage-powered spatial statistics, and overhauling the visualization pipeline to render rasters as a single ipyleaflet.ImageOverlay instead of millions of polygon draws. All work is aligned with Mesa 4.0's unified reactive architecture, positioning Mesa-Geo as the geospatial pillar of Mesa's next generation rather than a legacy bolt-on. Core deliverables: PropertyLayer-backed RasterLayer, decoupled Cell with three explicit coordinate properties, RasterCellCollection aggregation API, SolaraViz-compatible make_geospace_component, a geo predator-prey benchmark model, and a full Mesa-Geo 3.x migration guide. Stretch goals: H3 hexagonal grid support, a GeoSpace redesign proof-of-concept (#2585), and a Kalman filter temporal state estimation API for PropertyLayer.
<p>Servo has support for Web Workers, and the new Fetch Api whose development is in progress is another new standard, that aims to replace XMLHttpRequest (XHR), and provides a cleaner api for anything involving requests and responses.The Fetch api spec also has a subsection which details on handling fetch calls within a service worker context. <a href="https://slightlyoff.github.io/ServiceWorker/spec/service_worker/" target="_blank">Spec</a> Service Workers are the new standard, for modern web apps, which aims to bring native app like experience to browser based apps, by providing a programmable api, for caching certain paths of pages, ,manipulating routing within an application,intercepting network requests according to user logic.</p> <p>Servo has a partial implementation of Fetch api, but the Service Worker api’s are currently missing and if implemented, Servo will be able to intercept network calls made from within the Service Worker’s context, the “handle_fetch” subsection of the Fetch Spec, is to be implemented. <a href="https://fetch.spec.whatwg.org/" target="_blank">Spec</a></p> <p>My project is to have a partial implementation of the new Service Worker Api and its helper interfaces, in Servo. The project is focused on working on parts of the Service Worker Specification which revolves around intercepting network requests.</p>
<p>Livechat is a package that adds the ability to embed a pop-up support chat to your website. For example when you want to interact with users visiting your website and help them with their problems, then this feature of RocketChat helps you with that. All you need to do embed a script on to your static website. Live chat agents who wield this tool use it to make customers happy and satisfied.</p> <p>This project adds real-time monitoring to livechat which will be an important feature as this will be helpful for livechat agents in the following way:-</p> <ul> <li><strong>More information about the user</strong>:- Track important information related to visitors, such as the <em>current page, location, time on site, local time</em>, etc, even though the visitor has not yet started a conversation with an agent.</li> <li><strong>Edit Info Panel for livechat with the user</strong>.</li> <li><strong>Increase Response TIme</strong>:- Agent will be able to start a conversation with a specific visitor directly from the list, improving the proactivity of the Live chat team.</li> <li><strong>New Admin Panel providing more info of users</strong></li> <li><strong>Add sentiment analysis on user messages</strong>:- When chat will be closed, sentiment analysis will be applied on user messages and shown on the admin dashboard for future use.</li> </ul>
Astropy’s Python API is well-tested, but its underlying compiled layer (C, C++, Cython) lacks isolated testing. Because performance-critical extensions are currently only tested indirectly via high-level Python calls, deep bugs can easily be masked. This testing blind spot also blocks major architectural milestones, including the APE low-level package split, the Meson build system migration, and support for Python 3.15 free-threaded builds. This project will build a dedicated test suite to exercise each compiled extension module directly, entirely bypassing the public Python API. By engineering methods to probe these modules in isolation, including resolving complex runtime circular dependencies like `unit_list_proxy.c`; this work will establish a robust, reliable testing boundary between Python and the compiled code. Deliverables: C-API Audit: A mapped testing surface for active compiled extension modules. Isolated Test Suites: Direct pytest suites for compiled modules in astropy/table, time, timeseries, utils/xml, wcs, and erfa. Dependency Resolution: A C-level refactor (or minimal Python stub) to fix the `unit_list_proxy.c` circular dependency. Documentation: A new TESTING_EXTENSIONS.rst guide in Astropy's docs detailing how to run and extend these direct tests.
The multibeam sonar is a ray-based plugin designed to simulate the physics of acoustic signal propagation, including phase and reverberation effects. Originally developed for ROS 1 Noetic and Gazebo Harmonic as part of the DAVE project, it is currently being migrated to Gazebo Harmonic and ROS 2 Jazzy. This project aims to complete the migration and enhancement of the multibeam sonar plugin, with three main deliverables. The first is an enhanced plugin with improved performance through the introduction of half-precision calculations in CUDA. It is expected that this modification will greatly improve frame refresh rates. Numerical accuracy must be carefully taken into account when implementing it, however, and this should involve thorough testing and evaluation using quantitative metrics in comparison to the performance of the single-precision code. The second deliverable is the extension of simulation capabilities to support additional sonar types. Building on the existing multibeam sonar, it should be feasible to implement a side-scan sonar with for seafloor imaging, taking into account shadow analysis and directivity patterns like side lobes, for example. Finally, benchmark integration is essential to make the simulation more practical and accessible. This involves incorporating hardware that is often used in maritime robotics, like the BlueROV, and not only efficiently modeling the vehicle and its sensors, but also offering examples that are effortless to use. These benchmarks will enable the simulation to be validated and more available and beneficial for the general community, researchers, and developers.
Antrea provides [Network Policy APIs](https://github.com/antrea-io/antrea/blob/main/docs/antrea-network-policy.md) (in the form of K8s CRDs) for K8s cluster administrators and application developers to declare security rules in order to protect workloads. These APIs complement the [Network Policies supported natively in K8s](https://kubernetes.io/docs/concepts/services-networking/network-policies/). When using the Antrea-specific Network Policy APIs, it is possible to use Fully Qualified Domain Names (FQDNs) in order to select the list of external domains with which a K8s application is allowed to communicate, or forbidden from communicating. The current implementation of this feature is not compatible with applications which directly cache the result of DNS queries. We have found that this type of caching is frequent for Java applications, which greatly impacts the usability of FQDN-based security rules. We believe that by defining a new configuration parameter for the Antrea implementation, we can bypass the issue and ensure that the feature can be used even with such applications, providing of course that the parameter is set correctly by users. Expected Outcome: Definition and implementation of a new configuration parameter (`minTLS`) for the Antrea Agent, which will ensure that FQDN-based security rules can be used even with application that cache DNS results. The implementation should come with a sufficient amount of tests (both unit tests and e2e tests).
Observable Public Cloud Infrastructure for IoT Developers is a project to enhance the Eclipse Thingweb ecosystem. The overarching goal is to create a comprehensive observability solution that empowers IoT developers with the tools they need to build, test, and debug Web of Things applications more effectively. By integrating OpenTelemetry into node-wot, enhancing the Test Things infrastructure, and providing intuitive monitoring dashboards, the project aims to solve a critical challenge in IoT development: the lack of visibility into distributed systems behavior. This project will transform the developer experience by providing real-time insights into application performance, protocol behavior, and system health, ultimately leading to more reliable and maintainable IoT solutions. I've structured my approach into three interconnected layers: the Core Layer integrates OpenTelemetry directly into node-wot to standardize telemetry collection; the Infrastructure Layer enhances Docker Compose configurations with health checks and observability backends; and the Monitoring Layer provides actionable insights through custom dashboards and alerts. Drawing from my experience with AWS services, Azure Monitor, and containerization technologies, I'm confident I can deliver a solution that addresses the unique challenges of IoT observability. I'm particularly excited about making distributed tracing work across different IoT protocols, as this will provide unprecedented visibility into cross-protocol interactions that are common in real-world IoT deployments while working with a team to deliver results!
AMD chips, with their powerful x86 architecture, exceptional computing performance, and advanced NPUs, demonstrate significant potential in fields such as industrial automation, in-vehicle systems, and high-performance edge computing. Introducing AMD's robust general-purpose and heterogeneous computing capabilities into the KubeEdge ecosystem is crucial for handling increasingly complex and latency-sensitive edge AI applications.However, the deep integration, performance optimization, and best practices between KubeEdge and AMD's high-performance edge platforms—particularly their built-in NPUs and other hardware acceleration units—still require systematic exploration and validation. This project aims to establish a complete link between KubeEdge and AMD edge nodes, building a comprehensive edge computing solution from hardware deployment to NPU acceleration, thereby greatly enriching KubeEdge's hardware ecosystem. Expected Outcome: 1. Debug and support KubeEdge edge nodes running on AMD chips 2. Successfully deploying and managing edge application Pods on AMD-based edge nodes 3. Scheduling and managing AMD NPU resources through KubeEdge to achieve performance acceleration for edge AI inference applications. 4. Implement monitoring and metric collection for nodes, applications, and NPUs 5. Using KubeEdge to achieve the complete platform setup, configuration, and management from the cloud to AMD edge nodes 6. Complete hardware compatib.....
The RISC-V Certification Steering Committee is developing certification tests to prove that RISC-V processors conform to the ratified specifications. The goal of this mentorship project is to run the tests on as many open-source RISC-V cores as possible, and improve the usability of the tests, debug any issues found in the tests, and report any real bugs that might be found in the cores. This work will involve: * Identifying multiple open-source cores to test * For each core: - Develop a Unified Database (UDB) file specifying the extensions and parameters supported by the core - Implement trick box macros to trigger interrupts, print characters to a console, and terminate a simulation in a core- specific manner - Create a linker script appropriate to the memory map of the core - Compile the tests with the core-specific trick box and linker scripts - Run the relevant tests on the core * Identify and fix any problems in the tests that make them hard to run on a core * Identify and fix any problems with the flow or documentation * Identify and report any bugs found in the cores The work will start with Phase 0 tests of the RVI20 profile with the RV{32/64}IMACDF extensions in machine mode. As time permits, it will continue to the Phase 1 MC100 microcontroller profile with machine mode, traps, Zicsr, and Zicntr, and then to the Phase 2 RVA23 application processor profile with all privilege modes, vector and hypervisor.
<p>A long-standing issue with Haskell’s documentation tool Haddock is that it needs to effectively re-perform a large part of the parse/template-haskell/typecheck compilation pipeline in order to extract the necessary information from Haskell source for generating rendered Haddock documentation. This makes Haddock generation a costly operation, and makes for a poor developer experience.</p> <p>An equally long-standing suggestion to address this issue is to have GHC include enough information in the generated <code>.hi</code> interface files in order to avoid Haddock having to duplicate that work. This would pave the way for following use-cases and/or have the following benefits:</p> <p>1) Significantly speed up Haddock generation by avoiding redundant work.</p> <p>2) On-the-fly/lazy after-the-fact Haddock generation in cabal new-haddock and stack haddock for already built/installed Cabal library packages.</p> <p>3) Add native support for a <code>:doc</code> command in GHCi’s REPL and editor tooling (ghc-mod/HIE) similar to the one available in other languages (c.f. the Idris REPL or the Python REPL)</p> <p>4) Allow downstream tooling like Hoogle or Hayoo! to index documentation right from interface files.</p> <p>5) Simplify Haddock’s code base.</p>
<p>JuliaAstro organization provides astronomers with the tools to work with the Julia language. One of the latest packages is AstroImages.jl, which aims to allow researchers to visualize astronomical images coming from FITS files. It is meant as an interface to popular Julia packages like Images.jl and Plots.jl This package is now in its infancy stage. The goal of this project will be to introduce new features and make it useful.</p> <p>GOALS</p> <ol> <li>Allow users to Reproject and co-align different ImageHDU into one using their WCS header info</li> <li>Support 3 channel/band astronomical images (i.e different extensions like RGB, HSV, XYZ, Lab etc.) and handle interconversions while minimizing losses</li> <li>Integrate different plotting feature like zooming, grids, overlays, markers, labels etc. with AstroImage type.</li> <li>Allow interactive GUI based or script based plotting of astronomical images</li> <li>Designing interface and integration with Images.jl for operations like contour plotting, filtering, histograms, segmentation etc</li> <li>(optional) Some miscellaneous features like blending of images from different fits files, custom colourmap visualization</li> <li>Design distributable format (metadata specific) of these custom visualization</li> </ol>
Many Metasploit modules include documentation describing how to manually build vulnerable test environments. However, these setup steps are performed outside the framework and often vary between users, making exploit verification slower and less consistent. This project proposes a new Metasploit command, build_vuln, that automates the provisioning of vulnerable environments directly from within msfconsole. The command will resolve a module’s associated environment definition and launch the environment using OCI compliant container configurations. The system will support both Docker and Podman runtimes, including rootless execution, through a runtime abstraction layer that avoids tight coupling to a specific container engine. A health management component will ensure environments are ready before exploitation, while an in memory registry will track environments created during the active session and allow users to list, manage, and tear them down. The project will also introduce standardized reusable environment definitions that can be referenced by multiple modules. Selected modules that currently rely on manual Docker instructions will be refactored to use the new mechanism, and a CI integration prototype will demonstrate how these definitions can be reused for automated module verification. The final deliverables include the build_vuln command implementation, container runtime integration, standardized environment definitions, reference module refactoring, CI integration prototype, and comprehensive developer and user documentation.