g3nd is the official demo/showcase application for the g3n Go 3D game engine. It is a single Go binary that presents a windowed GUI (built on the engine's own immediate-mode GUI system) with a categorized demo tree. Users select demos that exercise the engine's capabilities: glTF/glb loading, PBR materials, animations (skinning, morph targets), audio (OpenAL), particle systems, post-processing shaders, and GUI widgets (tables, trees, sliders, form boxes, dock layouts). The application registers demos via Go's `init()` side-effect pattern: each demo package imports itself and calls `app.DemoMap["category.name"] = &struct{}{}`. The core `App` struct manages the scene graph, camera, orbit controls, and per-frame `Update` dispatch. The repository also vendors a large set of test assets (glTF sample models, Blender files, audio, textures) under `data/`. The architecture is a classic Go application: `main.go` imports all demo packages for their registration side effects, then delegates to `app.Create().Run()`. The `app` package owns the window, GUI, and demo lifecycle. Each demo implements a minimal `IDemo` interface (`Start`, `Update`, `Cleanup`). The `util` package provides reusable GUI helpers (file selectors, light meshes). The demos are grouped by category: animation, audio, experimental physics, geometry, GUI, light, loader, material, other, shader, texture. The code is idiomatic Go with clean separation, but some demos are marked experimental and the engine dependency is a pseudo-version that may drift.
rules_boost is a Bazel repository providing build rules for the Boost C++ libraries. It allows Bazel users to depend on Boost libraries using labels like @boost//:algorithm. The repository fetches Boost source code and provides platform-specific build configurations for hundreds of Boost components, handling separate compilation requirements for libraries like ASIO and Beast. While the README indicates it's legacy compared to Bazel Central Registry, it remains maintained for compatibility. The core reusable component is the boost_library macro in boost/boost.bzl, which encapsulates patterns for building C++ libraries with Bazel.
The 21-Points Health application is a full-stack health tracking system built with a Spring Boot backend and an Angular frontend. It allows users to register, log in, and track various health metrics including weight, blood pressure, and activity points (from exercises, meals, and alcohol). Users can set personal preferences such as weekly goals and weight units (kg/lb). The application provides data visualization through lists, calendars, and charts, and includes administrative features for user management. The architecture follows a standard monolithic pattern with a clear separation of concerns. The backend exposes a RESTful API secured with JWT authentication, uses Spring Data JPA for persistence with a PostgreSQL database (H2 for development), and integrates Elasticsearch for search capabilities. The frontend is a modular Angular application that consumes the API, implements reactive state management with RxJS, and uses Bootstrap for responsive styling. The application also includes internationalization (English and French), Docker Compose configurations for development dependencies, and monitoring setups with Prometheus and Grafana. While the application leverages the JHipster generator for much of its boilerplate, it contains several custom components that demonstrate good engineering practices. Notable among these are a custom Logback converter for handling multi-line log messages, a utility service for file operations (base64 encoding and blob downloading), and a pipe for formatting time durations. These components are relatively isolated and could be reused in other projects with minimal modification.
This repository contains a collection of example applications demonstrating the use of the gnet networking library in Go. The examples cover various networking paradigms including TCP, UDP, Unix domain sockets, HTTP, WebSocket, and a custom binary protocol. Each example is a standalone program showcasing event-driven connection handling, message parsing, and protocol implementation using gnet's APIs. Key examples include echo servers for different transports, an HTTP server using wildcat for parsing, a push server broadcasting periodic messages, a simple protocol client/server with a custom framing codec, and WebSocket implementations using both gobwas/ws and a custom RFC 6455-compliant codec. The code illustrates gnet's event loop patterns, connection context usage, and efficient I/O handling. While the examples are generally idiomatic and functional, some dependencies show mild technical drift (e.g., the wildcat HTTP parser is outdated). The repository is actively maintained with recent commits and serves as a practical reference for learning gnet-based network programming in Go.
Notion is a tiling, tabbed X11 window manager for keyboard-centric users, forked from Ion3. It provides a modular architecture with a C core (ioncore) and loadable modules (tiling, menu, query, statusbar, dock, multihead, etc.). Lua is the primary configuration and extension language, powered by the libextl library which auto-generates C-to-Lua bindings from annotated function declarations. The window manager manages a hierarchical region model (frames, workspaces, groups, clients) with dynamic dispatch via function tables. It includes a full-featured status bar system with a separate daemon (ion-statusd) and dozens of user-contributed meter scripts. Session management via XSMP, multi-monitor support (Xinerama/XRandR), and a remote-control socket (notionflux) are built-in. The codebase is mature but shows signs of technical drift: it relies exclusively on X11 (no Wayland), bundles a portable snprintf from 2000, carries legacy workarounds for long-obsolete systems, and many contrib scripts are unmaintained or broken. Nevertheless, the core architecture and utility libraries (libtu, libextl, libmainloop) are well-crafted and potentially reusable in other C projects.
ggprism is an R package that extends ggplot2 to replicate the visual aesthetics of GraphPad Prism. It provides themes, color/fill/shape palettes, and specialized geoms/guides to create publication-ready plots matching Prism's default styling. Key functionalities include applying Prism-like themes via `theme_prism()`, using discrete palettes with `scale_*_prism()` functions, adding statistical annotations (e.g., p-value brackets) with `add_pvalue()` and `geom_bracket()`, and customizing axes with specialized guides like `guide_prism_offset()` for offset ticks. The package follows ggplot2 extension conventions, using ggproto for custom geoms, discrete_scale for scales, and guide objects for axis modifications. It includes built-in datasets (e.g., wing morphology data) and relies on standard R datasets in examples. External dependencies center on ggplot2, scales, and rlang, with optional packages like ggnewscale and patchwork used in vignettes.
Nakarte is a client-side single-page web mapping application built with Leaflet and Knockout, specialized for outdoor activities like hiking, cycling, and mountaineering. It provides an extensive catalog of map layers (OSM, satellite, topographic, overlays) with a strong focus on European and Russian regions. The application includes comprehensive GPS track management: loading from files (GPX, KML, GeoJSON, etc.) and online services (Strava, Garmin, OSM, Wikiloc), editing, elevation profiles, and exporting to GPX/KML/ZIP or Garmin JNX format. Additional features include search with multiple providers, panorama viewers (Mapillary, Wikimedia), azimuth/distance measurement, coordinate display in various formats, map printing with page layout, session save/restore, and custom layer configuration. The architecture is a classic Leaflet-based SPA with Knockout for UI bindings, webpack for bundling, and a separate CORS proxy server for tile access. External dependencies include Leaflet, Knockout, protobuf for track serialization, and various external API services. The codebase shows signs of organic growth with legacy code patterns (vendored scripts, relaxed ESLint for old files) and mixed English/Russian comments.
LLMMap is a CLI-based automated prompt injection testing framework for LLM-integrated applications, modeled after sqlmap. It systematically discovers injection points (query parameters, headers, body, cookies, path), generates goal-aware adversarial prompts using a dual-LLM architecture (Generator + Judge), and evaluates responses through pattern matching, semantic similarity, and out-of-band callbacks. The tool supports 227 injection techniques across 18 attack families, multiple LLM providers (Ollama, OpenAI, Anthropic, Google), and provides reliability confirmation via Wilson confidence intervals. It includes comprehensive reporting, data-flow tracing, and Burp Suite integration. The codebase is well-structured with clean abstractions, extensive tests, and reusable components, though some modules are reserved for future development and external dependencies like interactsh-client introduce fragility.
This repository provides the complete hardware and software stack used to capture, process, and release the VR-NeRF Eyeful Tower Dataset, a multi-view, multi-camera HDR dataset of indoor scenes for NeRF research. It includes a C++ camera driver for controlling an array of Sony A1 cameras via the Sony Camera Remote SDK, a ROS2-based robot control system for a PAL TIAGo base, a Godot-based remote control application (Commandly) for teleoperation and monitoring, and a Python processing pipeline for HDR merging (Debevec, PPNE, robust PPNE), white balance, downscaling, JPEG export, and automated photogrammetric reconstruction using Agisoft Metashape. The dataset itself (22 scenes, up to 4.4 TB) is hosted on AWS S3 and includes HDR EXR images, JPEGs at multiple resolutions, camera calibration files (KRT, Metashape XML, COLMAP), 3D meshes, and train/test splits. While the primary deliverable is the dataset, the codebase is a hybrid of research data pipeline and application software, with the application components (camera driver, robot control, UI) serving the data generation process.
Blobby Volley 2 is a complete, cross-platform 2D multiplayer volleyball game implemented in C++ with Lua scripting for AI bots and game rules. It features local and networked multiplayer (client-server via a bundled, modified RakNet stack), a dedicated server for online matchmaking, replay recording/playback, and a custom immediate-mode GUI built on SDL2. The architecture uses a state machine pattern (State base class with derived menu, game, and replay states), abstracted rendering backends (OpenGL, SDL, Null), and a custom physics engine with integrated Lua-driven rule logic. The project is built with CMake and targets Windows, Linux, macOS, Android, and Nintendo Switch, with GitHub Actions CI for multiple compilers and platforms. The game's core loop processes player input (keyboard, mouse, joystick, touch, or Lua script) through an InputManager, feeds it into DuelMatch (which combines GameLogic and PhysicWorld for physics and rules), and renders via RenderManager. Network games use RakNet for reliable UDP communication with prioritized packet handling; the dedicated server manages lobbies, matchmaking, and state broadcasting. Replays are recorded as binary state snapshots (using GenericIO serialization) and can be played back in-game. The Lua API provides bot developers with real-time game state queries, physics prediction functions, and callbacks for serve and bounce events, along with older legacy scripts in data/scripts/old. While the codebase demonstrates solid engineering (template-based serialization, abstracted file I/O with PhysFS, cross-platform build systems), it carries technical debt from aging dependencies (RakNet, Lua 5.3, SDL2, TinyXML2) and heavy use of platform-specific ifdefs. Some components, like the custom IMGUI and RakNet integration, are tightly coupled and not easily extractable, but the GenericIO serialization layer and FileSystem wrapper are self-contained and could be reused in other C++ projects needing binary I/O or virtual file system access.
This repository is the official blog for the 'Web Dev Simplified' educational brand, built with Astro as a static site generator. It contains hundreds of MDX tutorial articles covering JavaScript, CSS, React, TypeScript, and other web development topics, published on a strict Monday schedule. The architecture is a static blog with selective client-side interactivity via React components (islands) embedded in articles to demonstrate concepts. Key infrastructure includes a custom theme system with light/dark mode, Plausible analytics with a custom proxy, ConvertKit newsletter integration, dynamic Open Graph image generation using Satori/Sharp, and a set of custom Remark plugins for YouTube embeds, responsive images, and syntax highlighting with line highlights. Deployment is on Netlify with redirect handling and RSS feed generation. The content creation pipeline is augmented by AI agent skills defined in the `.agents/` directory, which enforce a strict writing style and publishing workflow. While the codebase is well-organized and demonstrates solid engineering practices for a content site, it carries some technical debt including a pinned outdated Node.js version (v17.9.0), use of deprecated Shiki API, and a dead service worker that only self-unregisters. The docs/ directory contains comprehensive guides but has drifted from the actual code version (references Astro 2.4.5 while using 3.6.5). Overall, it is a well-crafted, feature-rich blog platform with reusable patterns in its utility modules and plugins.
Crystal Toolkit is a Python library and web application framework from the Materials Project for building interactive, browser-based visualizations and analysis tools for crystal structures and materials data. Built on Plotly Dash and pymatgen, it provides a set of reusable components (e.g., structure viewer, phase diagram, band structure, X-ray diffraction, Pourbaix diagrams, symmetry analysis) that can be combined into custom dashboards or used as standalone apps. The core architecture centers around an `MPComponent` base class that manages Dash stores, callbacks, and layout generation, and a `Scene` graph for 3D rendering (consumed by a Three.js-based component). The toolkit also includes utilities for export (Asymptote, POV-Ray) and JupyterLab integration via a MIME type extension. While primarily a library for application developers, it is tightly integrated with the Materials Project API and pymatgen for materials science data, making it a bridge between research data and interactive web UIs.
This is the idris2-lsp language server, a monolithic LSP server implementation for the Idris2 programming language. It provides standard IDE features such as go-to-definition, hover information, code completions, document symbols, semantic tokens, diagnostics, and various code actions including case splitting, expression search, and refactoring. It runs as a single process reading JSON-RPC messages from stdin and writing responses to stdout, leveraging the Idris2 compiler's API to load modules, resolve names, and perform type-checking. The server is built with Idris2 itself and depends on the lsp-lib library for LSP message types and encoding. While the codebase is well-crafted for its domain, it is tightly coupled to Idris2 internals and the LSP protocol, making it highly specific to the Idris ecosystem and not easily reusable outside that context.
volc-sdk-python is the official Volcengine SDK for Python, a programmatic client library for Volcengine cloud services. It is not a standalone application: it exposes service classes that wrap REST APIs and protobuf-defined services. The dominant architecture is a base Service class that handles credential resolution (AK/SK, environment variables, ~/.volc/config), request signing, and HTTP dispatch, while each service defines an api_info mapping from action names to HTTP method/path/query. Some services (TLS, Live) use protobuf-generated models; others use legacy ApiInfo-style raw dicts, creating inconsistent implementation styles across the SDK.
This repository is a Godot GDExtension that enables using Dart as a scripting language for the Godot game engine. It provides a C++ native plugin that embeds the Dart VM, a Dart runtime library (`godot_dart`) with FFI bindings and type wrappers, and a build runner package (`godot_dart_build`) for generating boilerplate code from `@GodotScript` annotations. A binding generator tool (`tools/binding_generator`) reads Godot's extension API JSON to produce Dart bindings for engine classes and built-in types. The repo includes two example projects: a 2D game tutorial and a networking demo. It is feature-rich but explicitly experimental, with partial support for debugging, hot reload, and editor integration, and acknowledges that performance optimization has not yet been performed. The architecture is a hybrid of C++ native extension and Dart packages with code generation pipelines, making it a complex but well-structured integration layer between the Godot engine and the Dart language.
PyMetis is a Python wrapper for the METIS graph partitioning library, providing a high-level API for partitioning graphs and meshes, and for computing sparse matrix orderings (nested dissection). The Python package exposes functions such as `part_graph`, `part_mesh`, and `nested_dissection` via pybind11 bindings to the bundled METIS 5.2.1 C source. The build system (meson-python) compiles the METIS library and GKlib utilities from source, producing a self-contained wheel. The repository also includes a comprehensive test suite that validates partitioning of 2D/3D tetrahedral meshes and graph-based partitions with weighted vertices and edges. While the Python API is clean and straightforward, the project's primary value lies in its reliable integration of a well-established, high-performance C library rather than in novel algorithmic contributions. The codebase is actively maintained, with regular releases, CI/CD pipelines for multiple platforms, and support for both PyPI and conda-forge distributions.
This repository provides implementations of the Dynamic Time Warping Barycenter Averaging (DBA) algorithm in multiple programming languages (Java, Python, MATLAB, and Cython). The DBA algorithm computes the average of a set of time series under Dynamic Time Warping (DTW) by iteratively aligning each series to the current average and updating the average as the mean of aligned points. The repository includes the core algorithm, a multivariate extension, and versions with warping window constraints. The primary implementation is in Python (DBA.py), which is self-contained and requires only NumPy. The code is well-structured and demonstrates the iterative DTW-based averaging process, which is a non-trivial approach to time series averaging.
AndroidDrive is a Windows desktop application that mounts Android smartphone internal storage and SD cards as drive letters using the Dokan user-mode filesystem driver and ADB (Android Debug Bridge). It is built with Qt6 (C++20) and CMake, providing a system tray interface, device list window, and per-drive settings (drive letter, auto-mount, language, hide dot files). The application communicates with Android devices via ADB commands, caches remote files locally for read/write operations, and pushes changes back. It supports 10 languages via Qt translations and includes an update checker that queries GitHub releases. The architecture is a single-process Qt application with a Dokan callback implementation for filesystem operations. Key entry points are main.cpp (application startup), androiddrive.cpp (core mount logic), and dokanoperations.cpp (filesystem callbacks). External dependencies include Qt6, Dokan library (v2.3.1), and ADB binaries fetched from a third-party GitHub repo. The codebase is well-structured but has some hardcoded paths and is Windows-only.
This repository is an Electron-based desktop developer tool for debugging Lynx applications, a mobile/web framework by ByteDance. It provides a full-featured debugging experience by forking and customizing the Chrome DevTools frontend, adding panels for DOM inspection, CSS editing, network analysis, console, performance profiling, and more. The tool connects to Lynx simulators or devices via WebSocket and IPC, enabling real-time debugging of mobile applications. The architecture consists of an Electron main process that manages IPC handlers, a debugger bridge, and platform-specific services, and a renderer process that hosts the DevTools UI built with React and LitHtml components. A plugin system allows extending the tool with custom panels and functionality, with built-in plugins for tracing and recording user interactions. The repository also includes a CLI tool for starting the platform and managing connections, and a web simulator for testing. The codebase is large and actively maintained, with extensive test coverage including unit tests, e2e tests, and accessibility validation. However, it carries significant technical debt from the Chrome DevTools fork, including legacy code, duplicated utilities, and complex build processes. The plugin system and custom ESLint rules are notable reusable components.
HILO-MPC is a Python toolbox for machine-learning-supported optimal control and estimation, developed at TU Darmstadt and Otto von Guericke University. It provides a comprehensive set of controllers (NMPC, LMPC, PID, LQR), state estimators (MHE, Kalman filters, particle filter), and machine learning models (Gaussian processes, neural networks) that can be integrated into control loops. The architecture is built on CasADi for symbolic differentiation and optimization, with a plugin system for backends (PyTorch, TensorFlow, scikit-learn) and visualization (Matplotlib, Bokeh). The toolbox supports ODE/DAE modelling, linearization, discretization, and code generation for embedded deployment. The codebase is organized into modules for controllers, estimators, dynamic models, machine learning, and utilities, with a clear base class hierarchy. Key reusable components include symbolic variable management (Vector, RightHandSide), hyperparameter optimization frameworks, kernel composition for GPs, and OPC UA connectivity for industrial control. The project includes extensive documentation, examples, and tests covering chemical reactors, bioreactors, robotics, and automotive applications. While primarily an application library for control engineering, it also incorporates research-oriented features such as stochastic MPC, path following, and hybrid modelling with learned components. The code is licensed under LGPL-3.0 and is actively maintained with CI/CD pipelines and regular releases.