Automation Gateway is a reactive, configuration-driven bridge for industrial protocols (OPC UA, MQTT, PLC4X) that routes real-time process data to multiple time-series databases (InfluxDB, IoTDB, OpenSearch, Cassandra, PostgreSQL, etc.) and exposes it via GraphQL, MQTT, and OPC UA servers. The system runs as a single JVM or GraalVM native binary, orchestrated through YAML configuration files that define driver instances, logger sinks, and server endpoints. Its core architecture is built on Vert.x event bus for internal pub/sub messaging, with abstract base classes (DriverBase, LoggerBase) enabling consistent extension for new protocols or data stores. The gateway does not persist data itself; it acts as a real-time router with configurable buffering and queue reliability (memory-mapped disk queue). Key entry points include `App.kt` for the main application and `GraphQLServer.kt` for the administrative API, which supports JWT authentication, health checks, and dynamic component management. External dependencies include Eclipse Milo (OPC UA), HiveMQ MQTT client, PLC4X, Apache IoTDB Thrift, InfluxDB HTTP client, and various database drivers. The codebase is mature (v1.38) with active development, but carries some technical drift in the form of deprecated features still present in source code and a large set of reflection configurations for GraalVM native-image that require careful maintenance.
ffmpeg-concat is a Node.js CLI tool and library for concatenating video files with OpenGL-based transitions. It extracts frames from input videos using ffmpeg, applies GLSL transitions between consecutive frames using headless-gl, and transcodes the result to MP4. The architecture is modular with separate modules for frame extraction, transition rendering, audio handling, and final encoding. Key entry points are lib/index.js (library API) and lib/cli.js (command-line interface). The system relies on ffmpeg as a system dependency and wraps it with fluent-ffmpeg for Node.js integration. The code demonstrates solid engineering practices with clear separation of concerns, proper error handling, and test coverage. However, the dependency ecosystem shows signs of age - many packages date to 2018-2019, and the Travis CI configuration uses outdated Node.js versions. The OpenGL-based transition system is the core innovation, allowing complex visual transitions that would be difficult to implement with ffmpeg filter graphs alone. This is a practical tool for video editors and developers needing programmatic video concatenation with visual effects. It's not a research project or data pipeline - it's a production-ready library with CLI support.
This repository is an unofficial fork of J2ME-Loader, a Java ME (J2ME) emulator for Android. It enables running MIDlets (Java ME applications) on Android devices by implementing J2ME APIs (LCDUI, M3G, MMAPI, etc.) and using native C++ components via JNI for performance-critical sections like 3D rendering (M3G) and audio synthesis (Sonivox, TSF). The emulator includes a user interface for browsing and launching MIDlets, configuring settings, and handling permissions. It also features a dex manipulation library (dexlib) for processing DEX files to ensure compatibility with Android ART. While the emulator is functional and demonstrates solid engineering practices, it shows signs of technical drift due to deprecated Android APIs and a forked dex library that may lag behind upstream, and maintenance appears stale based on commit frequency.
OplusEdlTool is a cross-platform desktop application (Avalonia UI / .NET) for flashing, backing up, and managing Oplus (Oppo/OnePlus) Android devices in Qualcomm EDL (Emergency Download) mode. The tool provides a graphical interface for reading partition tables, backing up individual partitions, merging super partition images from JSON definitions (super_def.json), applying firmware patch files, and verifying file integrity via SHA checksums. It integrates with Qualcomm's fh_loader.exe for low-level device communication and supports Oplus-specific ROM formats (.ofp, .ops). The application stores working data in LocalApplicationData, generates XML partition reports, and includes comprehensive logging. It is bilingual (English/Chinese) and explicitly warns users about dangerous operations like flashing the persist partition.
Material Motion for JavaScript is a reactive programming library designed for handling motion and gestures in web applications. It provides an observable implementation with operators similar to RxJS, gesture recognition components (Draggable, Swipeable, Tossable), physics-based animations using springs, and DOM integration utilities for connecting gestures to visual effects. The library enables developers to create interactive UI components by composing streams of events through operators to produce animated styles. The architecture follows a modular package structure with core library, demos, and testing utilities. The core library is organized by functionality: observables, operators, interactions, and DOM utilities. It uses TypeScript with strict typing and employs a build system using Rollup for bundling. Key entry points are in packages/core/src/index.ts and the various feature modules that export specific functionalities. The repository shows active maintenance with recent commits (last updated 2026-04-15), ongoing issue management, and comprehensive documentation. While there are some signs of technical drift in build tooling (older versions of webpack, rollup, and TypeScript in devDependencies), the core library code appears to be keeping pace with modern TypeScript practices and reactive programming patterns.
This repository is a comprehensive PyTorch library for person re-identification (re-ID), providing a full pipeline for training, evaluating, and deploying deep learning models. It includes a modular architecture with data managers (ImageDataManager, VideoDataManager), a large model zoo (OSNet, ResNet, DenseNet, HACNN, etc.), training engines (softmax, triplet, with video support), loss functions (cross-entropy with label smoothing, triplet with hard mining), metrics (CMC, mAP with Cython acceleration), and utilities (feature extraction, model export to ONNX/OpenVINO/TFLite, re-ranking). The codebase is well-organized into subpackages (torchreid.models, torchreid.data, torchreid.engine, etc.) and includes research projects (attribute recognition, deep mutual learning, neural architecture search). While the library is feature-rich and demonstrates strong engineering for its domain, it has not been actively maintained since mid-2022, relies on outdated dependencies (Python 3.6, torch 1.10), and contains deprecated API usage. It remains a valuable reference for re-ID practitioners but requires updates for modern environments.
This repository is a monorepo containing the `@react-google-maps/api` library, which provides React components and hooks for the Google Maps JavaScript API (v3.x). It includes sub-packages for InfoBox and MarkerClusterer overlays. The library is the primary product, offering declarative React wrappers for map features like markers, info windows, polygons, directions, street view, and more. The codebase also includes a full-stack web application (`web-app`) built with React Router v7, Hono, and Cloudflare Workers, serving as the library's documentation site, license sales platform, and user dashboard. The web-app features authentication, Stripe payment integration, multi-language support (9 locales), and a comprehensive interactive documentation page with code examples. The library itself follows a consistent functional component pattern with hooks for lifecycle management, but suffers from some code duplication and verbose event listener handling. The commercial license change in v3.0.0 may impact community adoption. Overall, the repository is actively maintained and functional, but not exceptionally polished.
ts-liveview is a full-stack real-time web application framework written in TypeScript, inspired by Phoenix LiveView. It enables building reactive user interfaces with minimal client-side JavaScript (~13KB gzipped) by rendering HTML on the server and applying incremental DOM updates over WebSocket. The architecture is a monolith: an Express server handles HTTP/WebSocket, SQLite (via better-sqlite3-proxy) persists data, and a custom JSX runtime serializes UI components into HTML strings. Client-side logic is limited to a lightweight WebSocket client (`ws-lite`) that interprets server-issued DOM commands (update text, attributes, append/remove nodes) by CSS selectors—no virtual DOM is involved. The framework supports multiple rendering modes (SSG, SSR, streaming, hybrid MPA/SPA), includes a rich set of reusable UI components (Router, Page, Navbar, Pagination, DataTable, Chart, ComboBox, etc.), built-in localization and i18n, rate limiting, geolocation logging, and PWA manifests. A suite of demo pages (thermostat, chatroom, form, upload, pagination, timeline) demonstrate real-time state synchronization across clients. External dependencies include Express, ws, knex, better-sqlite3, chart.js, swiper, ionic, and Prism.js for syntax highlighting. While the framework is functionally complete and exhibits strong engineering in its JSX AST handling and WebSocket update protocol, the repository includes many demo artifacts, placeholder templates, and a large surface area that may drift over time. The custom build pipeline (esbuild) is bespoke, and several components show code comments or `console.log` calls indicating development-stage code.
This repository is a React Native library that provides platform-specific camera and image/video picker functionality. It exposes two primary functions: `launchCamera` and `launchImageLibrary`, which allow users to capture photos/videos or select existing media from the device library. The implementation covers iOS (using UIImagePickerController and PHPickerViewController), Android (via Intents and the AndroidX Photo Picker), and a minimal web fallback using browser APIs. The library handles image resizing, metadata extraction, video conversion, permission handling, and offers configurable options like quality, media type, selection limits, and more. The codebase follows standard React Native native module patterns with support for both the old and new architecture (TurboModules). While the implementation is functional and well-tested by the community, it includes some code that could be considered dated (e.g., synchronous dispatch semaphore on iOS, inline DOM manipulation on web) and does not contain easily extractable reusable components outside its specific domain.
OptimaJet.Workflow is a .NET workflow engine library designed for business process management and automation. It provides a core runtime for defining, executing, and persisting workflow schemes (process definitions) across multiple database backends including SQL Server, MySQL, PostgreSQL, Oracle, SQLite, and MongoDB. The engine supports multi-tenancy, version control of workflow schemes, and includes a visual HTML5 designer for creating workflows. It is architected as a library/framework layer, intended to be integrated into applications rather than running as a standalone service. The codebase demonstrates a hybrid architecture, combining modern .NET Core samples with legacy .NET Framework implementations using Windows Workflow Foundation (WWF). This duality is evident in the presence of both `OptimaJet.Workflow.Core` (modern) and `Other/WorkflowFoundation` (legacy) directories. The library relies heavily on the Provider Pattern for persistence, allowing developers to swap database backends via dependency injection. It also features a robust migration framework (FluentMigrator for SQL, custom scripts for MongoDB) to manage schema evolution, particularly around multi-tenancy support (`TenantId` columns). While the library offers solid engineering patterns like generic database abstraction (`DbObject<T>`) and async/await persistence, the codebase suffers from significant technical drift. It includes deprecated technologies such as `System.Workflow` and WCF, and sample applications rely on older versions of frameworks like ABP (v6.5.0) and .NET Core 2.2. The duplication of persistence logic across five different database providers increases maintenance overhead and the risk of schema drift between implementations.
This repository contains the firmware for FreeJoy, a highly configurable USB game controller (joystick, HOTAS, steering wheel) based on the STM32F103 (Blue Pill). The firmware implements a composite USB device with joystick HID, custom HID (for configuration), and CDC (for SimHub telemetry). It supports a wide variety of input sensors (ADC, magnetic encoders via SPI/I2C), buttons (GPIO, shift registers), encoders, LEDs (matrix and addressable RGB), and PWM outputs. Configuration is stored in flash and managed via a companion PC tool. A separate USB HID bootloader enables firmware updates. The code is bare-metal, leveraging the deprecated STM32 Standard Peripheral Library and CMSIS 3.5.0, with SEGGER RTT/SysView for debugging. The architecture is monolithic but modular within the firmware, with clear separation between bootloader and application.
LogoAI is a Next.js-based web application that enables users to generate professional logos using AI models. The system provides authentication via Clerk, rate limiting through Upstash Redis, and stores generation history in a PostgreSQL database using Drizzle ORM. Users can create logos with customizable styles, colors, and AI models, then view their generation history or browse a public gallery of all generated logos. The application follows modern Next.js patterns with the App Router, server actions for data mutations, and a component-based UI using Shadcn UI primitives.
CloudSim is a discrete-event simulation framework for modeling and evaluating cloud computing infrastructures, services, and resource management policies. It enables researchers to simulate datacenters, hosts, virtual machines, containers, cloudlets, network topologies, power consumption, and workload scheduling. The framework is widely used in academic research for studying VM consolidation, energy efficiency, container placement, and network-aware application deployment. It includes real-world workload traces from PlanetLab and power models from SPEC benchmarks to support realistic experiments. The architecture follows a modular design with a core simulation engine (CloudSim, SimEntity, event queue) and a hierarchy of entities (Datacenter, Host, Vm, Cloudlet) that interact through pluggable policies. Key patterns include strategy-based allocation and scheduling (VmAllocationPolicy, CloudletScheduler), selection policies (SelectionPolicy), provisioners (RamProvisionerSimple), and power models (PowerModel). The project is organized as a multi-module Maven project with a core library (modules/cloudsim) and an examples module (modules/cloudsim-examples) that demonstrates various simulation scenarios. Primary entry points are CloudSim.init() and CloudSim.startSimulation(), with examples such as CloudSimExample1 (basic cloudlet simulation), NetworkExample1 (network-aware datacenter), and ContainerCloudSimExample1 (container-based simulation). Data flows involve creating datacenters with hosts, submitting VMs and cloudlets via brokers, and collecting results through logging and CSV output. External dependencies include Apache Commons Math, OpenCSV, Guava, and MaxMind GeoIP2 databases. The framework is primarily used for research in cloud computing resource management, with a focus on energy efficiency, workload consolidation, and performance evaluation. It supports extensions for power-aware computing, container virtualization, network simulation, web workloads, and geolocation-based latency modeling. While the core is well-structured, the codebase shows signs of technical debt such as deprecated methods, TODO comments, and duplicated boilerplate in examples.
This repository is a comprehensive toolkit for analyzing, optimizing, and transforming ONNX models. It provides a core library (onnx_tool) for loading models, performing graph analysis (shape/value inference), profiling computational complexity (MACs, parameters, memory), applying optimizations (operator fusion, constant folding), quantizing weights, and managing memory for efficient inference. The toolkit supports a wide range of model architectures including LLMs (BERT, GPT, LLaMa, MPT, Qwen), diffusion models (Stable Diffusion), computer vision (ResNet, EfficientNet), and multimodal models. Key features include a custom inference engine (GraphInfer) with memory pooling for zero-copy tensor views, a plugin-based node registry system for extending ONNX operator support, and utilities for model conversion and evaluation. The architecture centers around the onnx_tool package, which defines fundamental abstractions like Graph, Tensor, and Node. The Graph class handles model loading, shape inference, and transformation pipelines. The Node registry system allows dynamic registration of operation-specific handlers for shape/value inference and profiling. Optimization modules (fusion, quantization) work on the graph representation, while the inference engine (inference/infer.py) executes optimized graphs using a memory pool to minimize allocation overhead. Additional components include benchmarking scripts for performance analysis, model configuration management, and specialized support for LLM KV-cache handling. While the core library demonstrates solid engineering with reusable patterns like the node registry and graph rewrite framework, there are areas of technical drift due to loose dependency versioning and the broad scope requiring continuous maintenance to keep pace with evolving model architectures and ONNX specifications. The project appears maintained based on recent commit activity and community engagement (stars, forks, issue templates), though dependency management without version constraints poses a risk for long-term stability.
Se7en Pro is a Windows 10/11 anti-censorship VPN client that aggregates eleven circumvention protocols into one desktop application. In production it runs a Flutter glassmorphic GUI (Se7enFlutter) that talks over authenticated named pipes to a .NET 8 daemon (Se7enCore), which orchestrates child processes for Psiphon, Tor, Xray/sing-box, Aether (MASQUE/WireGuard/WARP), and SHARD (Cloudflare TLS fragmentation over VLESS/Trojan nodes). Chained multi-hop modes (Psiphon-over-WARP, Tor-over-V2Ray, etc.) are first-class features, and a Wintun/tun2socks TUN adapter provides system-managed routing with split tunneling by app, domain, and IP along with a kill switch, system proxy, DNS handling, LAN sharing, and admin elevation. Architecturally the daemon's ConnectionManager selects active engines behind an IConnectionEngine abstraction; LocalSocksEngineBase supplies a shared process-spawn/SOCKS5-probe/auto-restart lifecycle for every engine. The Flutter side is a Riverpod-driven dashboard with live speed/ping telemetry, engine-filtered log viewing, region picking, and a large settings surface. Primary data flows are: UI command → PipeCoreClient → IpcDaemonService JSON dispatch → ConnectionManager → engine process → local SOCKS5/HTTP proxy → system proxy or TUN; status and logs stream back over the same pipe. The daemon persists settings to settings.json, caches Aether edge pools, and fetches SHARD node lists from GitHub. The repo is hybrid in a narrow sense: it bundles curated operational datasets (Akamai/Cloudflare/Fastly IP ranges, Akamai seed IPs, SHARD seed nodes, Tor bridge strings) used at runtime for CDN fronting and edge discovery. These are static resource inputs to the application machinery, not research artifacts or pipeline outputs, so the dominant character is application. Craftsmanship is solid but uneven. The engine abstraction, IPC layer, Authenticode trust checks, DPAPI secret storage, and route-pinning logic are genuinely reusable. However, multi-thousand-line widget files (settings_page.dart ~2200 lines, split_tunnel_section.dart ~1200 lines), incomplete i18n coverage with hardcoded English/Chinese/Russian strings, version drift (UI reports v1.0.4 while the engine UA says 1.1.0), brittle relative resource paths, and bundled third-party binaries with limited update channels create real maintenance friction. Test coverage is thin (a few model/round-trip widget tests).
This repository is a comprehensive, structured library of over 50 marketing 'skills' designed for AI coding agents (Claude Code, Codex, Cursor, etc.). Each skill is a self-contained directory with a SKILL.md (frontmatter + workflow), a references/ folder with deep-dive documentation and benchmarks, and evals/evals.json for behavioral testing. The skills cover the full marketing lifecycle: copywriting, SEO, paid ads (Meta, Google, LinkedIn), email, social, CRO, pricing, offers, attribution, market research, and more. Additionally, the repository includes 40+ zero-dependency Node.js CLI scripts that act as API clients for marketing tools like Ahrefs, Semrush, GA4, Meta Ads, Mailchimp, etc., each following a consistent pattern with dry-run support and environment variable authentication. Several integration guides and a central tool registry (REGISTRY.md) complete the ecosystem. While primarily a content library, the CLI scripts and validation/sync tooling demonstrate strong engineering patterns. The skills are designed to be consumed by AI agents to execute complex, multi-step marketing tasks, with cross-skill references and a shared context document (product-marketing.md) enabling orchestration.
This repository is a curated collection of Git hook examples, organized by hook type (pre-commit, commit-msg, pre-push, etc.). Each hook type directory contains a README explaining the hook's purpose and one or more example shell scripts that demonstrate how to implement the hook for common tasks such as linting, branch protection, and commit message validation. The repository does not contain a runnable application but serves as a reference for developers looking to implement Git hooks in their projects. The example scripts are self-contained, written in POSIX shell or Bash, and rely only on standard Unix tools and Git commands, making them easy to adapt to various projects. While the hooks are simple, they illustrate practical patterns for enforcing code quality, preventing dangerous operations, and integrating with issue trackers. The repository is maintained with occasional updates, and the examples are relevant to current Git usage. The scripts are designed to be copied directly into a project's .git/hooks directory with minimal modification, often requiring only customization of variables like branch names or regex patterns.
Bob is a Scheme language implementation consisting of a Python interpreter, compiler, and virtual machine (VM), plus an optional C++ VM implementation (BareVM). The system compiles Scheme source code to custom bytecode, which can be executed by either the Python VM or the C++ BareVM. It includes features like bytecode serialization/deserialization and WebAssembly compilation. The architecture is modular with clear separation of concerns: parser, compiler, bytecode handling, VM execution, built-in functions, expression representation, and environment management. Key entry points are in bob/cmd.py (command-line interface) and example scripts demonstrating interpretation, compilation, and execution workflows.
SPIMemory is an Arduino library providing a high-level interface for SPI Flash and FRAM memory chips. It supports reading, writing, and erasing data of various types (byte, char, word, long, float, string, arrays, structs) across a wide range of microcontrollers (AVR, SAM, SAMD, ESP8266, ESP32, STM32, nRF52, etc.) and memory chip manufacturers. The library automatically identifies chips via JEDEC IDs and the SFDP standard (JESD216B), manages address allocation, and offers optional error checking and high-speed modes. It is not a standalone application but a reusable component for embedded firmware projects requiring external non-volatile storage. The codebase demonstrates solid engineering with template-based I/O, conditional compilation for platform support, and a consistent error-reporting pattern. However, it shows signs of technical drift: dual documentation systems (Sphinx and MkDocs) with stale build artifacts, outdated jQuery in docs, beta features (FRAM, ESP32 custom SPI), and some commented-out debug prints. The library is actively maintained (recent commits, version 3.4.0) but has 71 open issues, indicating ongoing development and community use.
The hCaptcha Vue Component Library provides Vue 2 and Vue 3 components for integrating hCaptcha into Vue applications. The library consists of two packages (@hcaptcha/vue-hcaptcha for Vue 2 and @hcaptcha/vue3-hcaptcha for Vue 3) built from a shared Vue component source. The component handles loading the hCaptcha API script, rendering the widget, and emitting events for verification, expiration, and other hCaptcha callbacks. It also provides methods to programmatically execute and reset the challenge. A notable utility in the library is the script loader (hcaptcha-script.js) which ensures the hCaptcha API is loaded only once per page using a promise-based pattern. This utility is framework-agnostic and could be reused in other projects requiring singleton script loading. The repository is set up as a monorepo using Lerna, with separate build processes for Vue 2 (using Vue CLI) and Vue 3 (using Vite). While the component itself is well-maintained and functional, the build toolchain shows signs of technical drift with outdated dependencies (e.g., Vue CLI 3, Vite 2, Jest 26). The project is actively maintained with CI pipelines for building, testing, and releasing new versions.