Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
<p>Many users of Open Ephys are using optogenetic tools to manipulate activity in genetically defined neural circuits, but there is currently no way to control these tools from the Open Ephys GUI. <a href="http://www.open-ephys.org/cyclops/" target="_blank">Cyclops</a> is a high-precision LED driver designed for precise optogenetic stimulation. Setting up a controlled closed-loop experiments, <em>where neurons can be stimulated based on real-time acquired neural data</em>, would be greatly simplified if a plugin to communicate with Cyclops is built into the GUI.</p> <p>A typical scenario would be to upload or stream waveforms to Cyclops and trigger their deployment <em>(or transformations)</em> based on events detected in GUI. An <strong>open communication protocol</strong> needs to be defined for this and also <strong>special programable processors</strong> that can generate feedback signals and control Cyclops <em>(via the protocol)</em>.<br> After configuring the processors in the pipeline, the GUI would program Cyclops and the experiment can be launched.</p> <p>In addition to this, a more powerful and upgraded Cyclops that uses a <a href="http://www.pjrc.com/teensy/" target="_blank">Teensy</a> board will be released. Cyclops and Open Ephys would still support the Arduino version though.</p>
This projects aims to bring the well known ColBERTv2.0 information retrieval system to Julia! In this project, we aim to implement various components of the ColBERT model, with the major focus on indexing and search. Being a late-interaction retrieval system, ColBERT isolates all the computations between the queries and documents to enable pre-computing the document embeddings offline. Combined with a RAG pipeline as an embedding and retrieval backend, ColBERT can make the usage of existing AI tools really powerful. As part of the project, we also aim to apply this model to Julia's own extensive documentation (over thousands of packages), and integrate ColBERT with AIHelpMe.jl and PromptingTools.jl. Combine this with a locally hosted LLM, all Julia users get a powerful, modular, and easily hackable local AI assistant, allowing them to integrate ColBERT with their own RAG pipelines. The main deliverable of the project will be a new package (called ColBERT.jl), with the implementation design inspired from the original Python implementation of ColBERTv2.0 (i.e the centroids + residuals compression method). The project will also have an extensive number of addons, including, but not limited to, implementing the training module for this package, which will allow users to train their own ColBERT models instead of relying on pretrained checkpoints, and distributed training (using existing art like DaggerFlux.jl).
<h4>Cross-language analysis of U.S.-Russian relations (Task 3)</h4> <p>Tweets from US democrats (or just anyone actively opposing Trump's presidency) and Russian conservators (or anyone supporting government) are collected and brought to a common denominator via translation-based and non-translation cross-lingual methods. Resulting corpus would be fascinating to research through several perspectives: for example get the political views through speech analysis, comparison of similarities in the vocabulary between people of similar and different political views, etc. Information can be retrieved through the Twitter API (Search or Stream, using Tweepy library).</p> <h4>Early Alzheimer syndrome detection in speech analysis (Task 9)</h4> <p>Research showed that it is possible to detect early signs of Alzheimer Syndrome in speech. I propose to train a model, which will learn to do it (and later make an app, assisting people with the high risk of Alzheimer). Data can be extracted from the Talk Bank (<a href="https://dementia.talkbank.org/" target="_blank">DementiaBank</a>) or, for example, <a href="https://dementiadiaries.org/" target="_blank">Dementia Diaries</a> website. The app could prompt their users to talk about their day and using speech recognition module could analyze the possibility of Alzheimer and changes overtime.</p>
Performance benchmarking distributed systems (such as DLTs) is a challenging task, comprising of multiple aspects, such as scalable workload generation, representative workload definitions, and comprehensive data analysis. Hyperledger Caliper is a general-purpose benchmarking tool with the goal of mitigating the aforementioned aspects of performance benchmarking: 1. It provides a flexible architecture to allow scalable workload generation. 2. It collects and reports results based on detailed client-observable execution traces. 3. It allows the implementation/plug-in of custom workload behaviors to meet the diverse criteria of a wide range of business scenarios. The flexible support of the aforementioned performance benchmarking aspects inherently makes the setup and configuration of a Caliper-based project cumbersome and error-prone: - The user must provide information about the system under test (SUT) in the form of a network configuration file. - The user must also specify the flow of the benchmark run in the form of a benchmark configuration file. - The runtime behavior of Caliper components can be influenced in detail through a configuration file. - As with most programming-related projects, a Caliper-based project should employ best practices to make its structure flexible and maintainable. The goal of the mentorship project is to deliver a Visual Studio Code extension that can help users perform the aforementioned tasks in an assisted and possibly automated manner.
<p>Currently, the ways to flash images in BeagleBone hardware are not easy especially for beginners, SD card method takes up much time and manual configuration, BBBlfs flashing tool works but is CLI based, not much reliable and works on limited platforms, TI's Uniflash tool is also old and works only under older versions of Windows and Linux with a lot of manual configuration. The project is to port the BeagleBone bootloader server BBBlfs(currently written in c) to JavaScript(node.js) and make a cross platform GUI (using electron framework) flashing tool utilising the etcher.io project. This will allow us to have single code base for a cross platform tool.</p> <p>The tool works as:</p> <ol> <li>TFTP transfer of SPL binary and u-boot.</li> <li>Utilizing the ums feature of u-boot, booting the BB hardware into USB mass storage mode.</li> <li>Flashing the BB hardware with etcher.io like tool. </li> </ol> <p>This project project will be really helpful for everybody especially newbies, who would have a nice experience with flashing images easily and faster, so that they can focus on the more important stuff be it their robotics project, kernel development or some new PRU hack.</p>
The goal of this project is to enable support for the High-Level Shading Language (HLSL) in clangd, allowing shader developers to benefit from modern language-server features such as code completion, diagnostics, semantic highlighting, and symbol navigation. Although HLSL is largely based on the C++11 standard and can already be parsed by Clang, clangd’s support remains incomplete due to missing handling of HLSL-specific constructs, semantics, and resource types. Additionally, shader development introduces unique challenges, such as multiple entry points within a single file (e.g., vertex and pixel shaders), which are not fully addressed by clangd’s current architecture. The project will begin with an evaluation of clangd’s behavior on HLSL code to identify gaps, followed by the design of appropriate extensions. An RFC will be proposed to the LLVM community to validate the design and gather feedback. Based on this, the project will implement key improvements to clangd, focusing on built-in function completion, semantic analysis of shader constructs, improved diagnostics, and better handling of shader-specific configurations. The final deliverables include a documented analysis of current limitations, an RFC describing the proposed design, a structured set of implementation issues, and upstreamed improvements to clangd, along with test coverage and documentation.
<h3>Modular YAMPL</h3> <p>The project fundamentally consists in developing a flexible plugin system that allows YAMPL to selectively load essential components at runtime. This makes YAMPL extremely modular and decoupled from the IPC backend modules, making it easy for anyone to add new backends or edit the existing ones without compromising the core YAMPL code.</p> <p>In addition to the plugin system, the project proposes an overhaul and development of a python binding generation procedure which allows for continuous generation of the bindings whenever the core code is modified. The ultimate goal of the project is to make YAMPL more flexible, modular and extensible.</p> <h4>How is Modular YAMPL possible?</h4> <ul> <li>An ABI-agnostic plugin middleware handles the runtime dynamic loading of the plugins, the communication between the YAMPL core code and the plugin as well as the marshalling of data. This system is designed with simplicity in mind and aims to be as <strong>solid</strong> and <strong>reliable</strong> as possible.</li> <li>A specifically designed open-source library (<a href="https://github.com/pybind/pybind11" target="_blank">PyBind11</a>) allows for seamless operability between C++11 and Python. This allows for an easy generation of the python bindings for all the core YAMPL primitives and data structures.</li> </ul>
This project aims to integrate the Sloan sparse matrix ordering algorithm from the Boost Graph Library into pgRouting, enhancing its capabilities for graph optimization for both undirected and directed graphs. The Sloan algorithm generates optimal vertex ordering that reduces profile and bandwidth of graphs, significantly improving the efficiency of matrix operations in network analysis applications. While pgRouting includes several matrix manipulation algorithms, it lacks specific matrix ordering algorithms like Sloan ordering that are essential for optimizing sparse matrices in network analysis. Current workarounds require users to export data to external tools, breaking workflow continuity. I plan to develop a new function pgr_sloanOrdering() with complete integration, comprehensive error handling, and support for both directed and undirected graphs. The implementation will leverage the Boost Graph Library's existing algorithm with careful adaptation to pgRouting's architecture. The project deliverables include a fully implemented Sloan ordering algorithm integration, comprehensive documentation and usage examples, an extensive test suite with performance benchmarks, and support for various graph types with configurable parameters. This project will benefit the community by expanding pgRouting's graph analysis capabilities, particularly for applications in transportation networks, utility network management, and scientific computing where matrix ordering significantly impacts computational efficiency.
During late-night beam tests, physicists must leave detector halls to find workstations with Qt installed just to check satellite status. This project creates a browser-based interface that lets researchers monitor and control Constellation experiments from any device on the lab network without installing software. The project delivers three components: (1) upstream contributions to Constellation's Python API adding callback mechanisms for satellite state changes and discovery events, plus porting C++ topic management classes to Python; (2) a WebSocket bridge wrapping ScriptableController and MonitoringListener via multiple inheritance to expose satellite control and monitoring to browsers; (3) a SvelteKit frontend implementing the full satellite state machine for real-time control and monitoring. I have verified the multiple inheritance approach through hands-on testing. Discovery, commands, heartbeat state tracking, and CMDP log callbacks all work through a single combined class. I also created a custom satellite and controlled it through the complete FSM cycle. Deliverables include merged upstream MRs for callback APIs and topic management, a working WebSocket bridge with callback-driven state updates, a browser dashboard with state visualization and command controls, a log viewer mirroring Observatory's subscription model, comprehensive documentation, and tests.
The convergence of blockchain and 5G security presents an opportunity to redefine authentication mechanisms within the core network. Traditional OAuth 2.0 authorization mechanisms in 5G rely on centralized components such as the Network Repository Function (NRF) to verify NF identities and issue access tokens. This introduces risks, including single points of failure, insider threats, and identity spoofing. This research explores a decentralized trust model for NF authentication using blockchain-based OAuth 2.0 authorization. The study will analyze the feasibility of leveraging blockchain smart contracts for secure, verifiable access token issuance, ensuring immutable NF identity records and distributed validation. By integrating blockchain with an open-source 5G core, the project aims to enhance security, mitigate attack vectors, and reduce dependency on centralized trust anchors. Expected Outcome and Deliverables - Design and prototype of a blockchain-integrated OAuth 2.0 authorization mechanism for NF authentication. - Implementation and testing of the system using an open-source 5G core solution. - Performance benchmarking against traditional NRF-based authorization models. - Security evaluation covering resilience to identity spoofing, insider attacks, and token misuse. - Documentation and research insights into blockchain-driven 5G security enhancements.
*OPEN TO US BASED STUDENTS ONLY* - Accepting applications until May 23, 2025 To profile, analyze, and optimize Redis access patterns in SONiC's critical services and daemons, with the goal of reducing unnecessary Redis traffic and ensuring responsiveness even under load. Implement robust exception handling for Redis to prevent daemon crashes. Probable Implementation: Review GET/SET operations to ensure appropriate exception handling is in place. Use tools like redis-cli MONITOR, strace, perf, syslogs to identify: High-frequency Redis accesses Redundant or repeated GET/SET patterns Long response-time operations Focus on critical daemons like chassisd, pcied, lldp, syncd, orchagent. Apply the following optimizing methods for best performance: Use "HGETALL" instead of multiple "HGET" operations. Check for value-change before writing. Batching and use pipelining where it is missing. Benchmarking: Setup baseline Redis load tests and focus on couple of high CPU/mem consuming HWSkus Compare before/after metrics Redis command frequency Memory and CPU usage Expected Outcome: - High-level document outlining of existing Redis baseline, improvements required, etc. - Optimized Redis access operations - Improved exception handling for Redis reads/writes
The basic features in an Election DApp are user registration, election creation, voting and result calculation. To make our DApp more flexible and user friendly, we need to add more voting algorithms apart from General Voting Algorithm. The three important features that need to be implemented are 1) Open and Invite based elections. 2) Authentication and user KYC. 3) Multiple algorithms to conduct elections. To implement these features, I would first work on the algorithms which will be written in Solidity. The front-end part will use Reactjs. For KYC verification, I'll use IPFS to store the document and encrypt the file. The admins can decrypt the file when verifying. This process of encryption, decryption and verification can be handled using Solidity. There is also an option to create open elections or invite-based. Invite-based elections can be done using EmailJS and SendGrid to send the election link to the email. Since these links can be shared, there will be a check to ensure that only the invited voter is voting. To increase user engagement, we will provide a domain `abc.voter` to get them identified as a voter for using our platform. This domain will also mint an NFT and the voter now has it. There are several other features that I would add such as "Extend Election Dates", "Restrict Past Dates", "Logout functionality", "Profile Edit", and "Improve the UI".
One possible way to use the Kubernetes API to connect to the KubeVela Control Plane in the background and fetch the required information like X-Definitions, ComponentDefinitions, TraitDefinitions, PolicyDefinitions, and WorkflowStepDefinitions. The plugin can then use this information to provide syntax highlighting and autocompletion for these definitions in the YAML files. To preview the rendering result of components and traits, the plugin can use the Kubernetes API to create a dry-run of the KubeVela application on the remote cluster. The output can be displayed in the IDE to give users an idea of how the application will look when it's deployed. To compare the difference between the current application configuration and the corresponding one on the remote cluster, the plugin can use the Kubernetes API to fetch the current configuration and compare it with the local one. The differences can be highlighted in the IDE for easy identification. To preview the selected clusters by the topology policy, the plugin can use the Kubernetes API to fetch the list of clusters and display them in the IDE. The plugin can also use the Kubernetes API to fetch the topology policy and apply it to the list of clusters to display the selected clusters. For ComponentDefinition and TraitDefinition, the plugin can use the CUE language to provide validation for the CUE input and preview the rendering result. The plugin can also use the Kubernetes API to fetch the ComponentDefinition and TraitDefinition and display them in the IDE for reference.
This project enhances the OpenAFS Linux kernel module with multi-page folio support, addressing a key performance limitation in the current implementation. OpenAFS currently interacts with the Linux kernel's memory management system through single-page operations, despite recent kernel versions offering folio APIs capable of managing multiple contiguous pages as a single unit. I will implement comprehensive multi-page folio support in OpenAFS by modifying key components of the cache manager, particularly focusing on the VFS interface layer where the largest performance benefits can be realized. The implementation will optimize read and write paths to efficiently handle larger memory regions while maintaining backward compatibility with older kernel versions through autoconf detection and conditional compilation. By the end of the project, I will deliver: (1) A complete implementation of multi-page folio support that improves performance, especially for sequential read operations common in application deployment; (2) A comprehensive testing framework verifying functionality across multiple kernel versions; (3) Detailed performance benchmarks demonstrating throughput and resource utilization improvements; and (4) Thorough documentation of implementation details to facilitate future maintenance. All code will be submitted as incremental, well-structured patches adhering to OpenAFS coding standards.
<p>The aim of this project is to enhance some portions of the application that implement the Internet Message Access Protocol (IMAP). Specifically :</p> <h5>CONDSTORE</h5> <p>The Conditional Store extension, defined in <a href="https://tools.ietf.org/html/rfc7162" target="_blank">RFC 7162</a>, adds an additional mod-sequence value to every message. This makes it possible to reference changes made to the mailbox made since a particular point in time, which is extremely useful for mobile clients that are not always connected to the internet. Adding support for the CONDSTORE extension will help to greatly reduce the time and data spent on resynchronization.</p> <h5>Search</h5> <p>K-9 Mail has a basic search feature that searches the local database as well as the remote server for messages. The project aims to add features that make it more modern, such as suggestions, nested search, filters and proper full-text search.</p> <h5>Miscellaneous improvements</h5> <p>Support for some additional IMAP operations will also be added :</p> <ul> <li>Using the UID EXPUNGE command when available so that messages deleted by other clients are not expunged by accident.</li> <li>Switching between and modifying namespaces.</li> <li>Moving messages across different IMAP accounts.</li> </ul>
<p>Pocket Science Lab at FOSSASIA aims to develop open source hardware & software technology to improve science education in the developing world. The main component of PSL is ExpEYES, an open source hardware and software framework for developing science experiments. (<a href="http://expeyes.in" target="_blank">http://expeyes.in</a>)</p> <p>This proposal aims to develop open science experiments for various branches of Physics. It also aims to continue improvements in the work done during my GSoC-2015 project “Sensor Plug-ins, Add-on devices and GUI Improvements for ExpEYES” (<a href="https://goo.gl/2B2CNO" target="_blank">https://goo.gl/2B2CNO</a>). The sensor plug-ins developed during GSoC-2015 project will be used for designing new low-cost experimental set-ups.</p> <p>The new development that will be undertaken is adding wireless node module for accessing sensors with PSL. This will enable PSL to fetch data from various sensors wirelessly and it will be useful in many experiments involving oscillatory and rotatory motions. Development of low cost modules for characterization in Physics research for example - study of sound and light absorption, measurement of thermal conductivity etc, is yet another important feature of this project.</p>
This project represents the orbit of a satellite orbiting earth on an Arduino-controlled pointer and a Liquid Galaxy rig through a mobile application. The application offers a unique way to visualize satellite orbits using the Liquid Galaxy rig (Google Earth) and a real-world Arduino-controlled pointer. It also provides insights into satellites' movements and access to vital satellite information seamlessly within the app. I plan to develop this by getting all the satellite data from SatNOGS database through API calls. Then, we use SGP-4 model to convert TLE of a satellite to get the state (position and velocity). Then we convert the satellite state to KML format. We segregate the KML data into the various tracks to get a neater visualization of the satellite's orbit data. Then, we write the code to send KML data from our Flutter app to the Liquid Galaxy to visualize this data on the Liquid Galaxy rig. Next, we make Arduino controlled pointer which emits green laser in the direction of satellite, which is controlled by the app. First, we 3D print the STL files of the 3D projector. Then, we assemble all the components of the Arduino-controlled pointer. Then, for the application, we use flutter_bluetooth_serial package to connect and send data to HC-05 module. Then, we use SGP-4 model to get the servo motor angles for the Arduino pointer. Then, we upload code to Arduino to receive data.
capa is an open-source tool that identifies program capabilities using an extensible rule set. Currently, the project relies purely on static analysis of code structures to identify patterns. This project extends capa to work on dynamic execution data such as sandbox run traces or code emulation analysis. The introduction of dynamic analysis to capa is set to make analyzing samples that feature anti-analysis techniques a much easier task. This is an issue of concern since a large number of distributed software nowadays gets packed with commercial or private packers, which means that capa would fail to profile these executables' capabilities successfully. However, this can be circumvented by introducing dynamic analysis to the problem, which it would enable capa to get a view of the program after it had been unpacked in memory, thereby making it possible to extract the capabilities from the executable at hand. Deliverables: 1. Add support for the future integration of several sandbox solutions by means of an associated feature extractor. 2. Implement a feature extractor for the Cuckoo-based CAPE Malware Configuration and Payload Extractor. 3. Introduce capa features that are specific to dynamic analysis (such as captured network traffic). 4. Add dynamic-based support for function call arguments. 5. Write novel rules that make use of the newly introduced dynamic capability extraction.
<p>The idea is to</p> <ul> <li>Add a new Database honeypot module - as for now there are modules like ssh,ftp,https and ICS but no module for catching database events.</li> <li>Add telenetsrv honeypot module to the system - as for now there are modules like ssh,ftp ,https and ICS.</li> <li>Add IMAP honeypot Module to the system - as for now there are modules like ssh,ftp ,https and ICS.</li> <li>Add SMTP Honeypot Module to the system - as for now there are modules like ssh,ftp ,https and ICS.</li> <li>Enhance the Web UI - Search functionality in the UI and also make the visualizations more better and presentable.</li> <li>Make small changes like export the data via UI and after the termination of the honeypot server in a nicely formatted JSON and CSV - currently only stored in the database.</li> <li>Add tests for all the functions inside the modules - as we have newly created the Test environment, I would like to add tests in the system.</li> <li>Docker Image - The idea is to create a docker image of the Honeypot process as currently one has to run it via script. To automate this process I would like to make a Docker Image and put it on Docker Hub to make it easier for some other company/user to use the Honeypot system.</li> </ul>
<p>This mobile app will be used to tell user about CO2 emission during user’s activity . This app will find the type of activity and distance travelled . Based on activity type and distance travelled by user , CO2 emission will be measured by using same formula used in existing browser extensions . This measurement will be real time , i.e. , user will be notified about CO2 emission at same time while he/she is travelling . This app will also contain Google Map to show user about his/her source and destination which will help user in navigating the path ( Having less CO2 emission) along with current information about CO2 emission .</p> <p>Platform Used - This mobile app will be developed as a Hybrid app . For Hybrid app development , React Native framework will be used along with Scala.js to make it cross-platform and easy to develop and maintain .</p> <p>Functionalities provided by Mobile app -</p> <ol> <li>Google account authentication </li> <li>Google Map showing path (having less CO2 emission) between source and destination</li> <li>Details about CO2 emission and its calculation</li> <li>Other features like 'learn more about Carbon Footprint' , 'set CO2 emission rate of user’s vehicle' , 'logout' etc.</li> </ol>
This project focuses on creating clear, approachable, and practical documentation that shows how to integrate kgateway’s AI Gateway (agentgateway) with popular AI tools, developer UIs, and other CNCF ecosystem projects. Its aim is to make kgateway’s documentation more practical, discoverable, and reflective of real ecosystem usage, so users can better understand what’s possible and how kgateway fits into the broader AI and cloud-native landscape. Examples of integrations and tutorials include: 1. Open WebUI / OpenAI Codex / Claude Code: Step-by-step guides showing how to connect agentgateway to interactive UIs for testing, demos, and common integration patterns 2. Demonstrate how agentgateway fits into the CNCF ecosystem by integrating with tools such as: a. Argo Rollouts: Update the Argo Rollout Gateway API guides with the latest agentgateway example config. Create docs using Argo Rollouts with AgentgatewayBackends for LLM providers and MCP servers. b. KServe: Using agentgateway as an ingress for model serving, enabling rate limiting, authentication, and observability c. Knative: Add a guide for setting up kgateway with agentgateway as a custom ingress gateway Expected Outcome: 1. A series of integration guides and tutorials demonstrating how to use kgateway with AI developer tools and CNCF ecosystem projects 2. New examples, improvements, and documentation pages....
OpenTRIM is a C++ Monte Carlo simulation framework that models the interaction of ions with matter, tracking energy deposition and defect creation. Currently, it includes a fixed tallying system for recording standard outputs, such as energy lost to ionization or defects. This project aims to extend OpenTRIM's capabilities by implementing a flexible, user-customizable tally system. The new tally system will allow users to define, via JSON configuration, what simulation events to track (e.g., ion stopping, vacancy creation), how to bin data (e.g., in cylindrical or Cartesian coordinates), and what physical quantities to record (e.g., ion depth, deposited energy). It will be implemented as a new class hierarchy in C++, inheriting from the existing tally class, and will make use of the ArrayND data structure for multidimensional data storage. Deliverables include: a) A customizable tally class with support for user-defined event handling b)JSON-configurable tally setup (geometry, energy bins, spatial bins, etc.) c) Sample tally implementations (e.g., ion range profiling) d) Unit tests, documentation, and tutorials for extending the system This work will empower researchers and developers to tailor OpenTRIM output to their specific simulation needs, improving its usability and scientific value.
LLM agents built with LangGraph and LangChain retrieve documents, call tools, and write to memory - but nothing validates what enters the model's context. A poisoned RAG document can hijack an agent's behaviour. A malicious tool parameter can exfiltrate data. A single memory write can silently alter every future response. There's no standard security layer for any of this. ACF-SDK is a Zero Trust firewall that sits between the agent and the LLM - intercepting every input across four hooks (prompt, context, tool call, memory) and enforcing policy-as-code decisions through an isolated Go sidecar. I want to take this pipeline from hardcoded ALLOW to real enforcement: upgrade the semantic scanner to catch paraphrased attacks, wire scanner signals into the real sidecar, build memory write protection with HMAC and provenance tracking, ship a Docker demo anyone can clone and run in 5 minutes, and stress-test the whole system against adversarial evasion techniques with a technical evaluation report. The foundation is already built. I've shipped 6 PRs - semantic scanner, benchmark harness, LangGraph adapter, Rego policy templates for all four hooks, audit logger, and a Go scan stage implementation. 155 tests passing. GSoC wires these components into a running system and proves they hold up under real attacks.
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.