This repository provides an Arduino library that implements the Bluetooth Low Energy MIDI (BLE-MIDI) transport layer, enabling Arduino boards to send and receive MIDI data over BLE connections. The library works with the FortySevenEffects Arduino MIDI Library and supports multiple hardware platforms including ESP32 (with both standard BLE and NimBLE), ArduinoBLE (NANO 33 BLE), and nRF52. The architecture features a clean separation between the core BLE-MIDI protocol implementation and hardware-specific adaptations. The transport layer correctly handles timestamp generation per the BLE-MIDI specification, running status optimization, and buffer management. Hardware abstractions use C++ templates to provide a consistent interface across different BLE stacks while exposing platform-specific configuration options.
nocc is a distributed C++ compiler system designed to accelerate C++ compilation, particularly for large projects with frequent rebuilds. It consists of three main components: a lightweight C++ wrapper (`nocc`) that pipes compiler commands to a Go daemon (`nocc-daemon`), which in turn coordinates with Go-based compilation servers (`nocc-server`). The system uses remote source and object caching to avoid re-uploading unchanged files and recompiling unchanged code, features an own includes parser for faster dependency detection than invoking the C++ preprocessor, supports precompiled headers compiled remotely, and provides local fallback when remote servers are unavailable. The architecture maintains persistent gRPC connections between daemons and servers while client processes start and die per compilation job, making it well-suited for build systems like CMake or KPHP that launch many parallel compilation processes.
This is a monorepo providing a feature-rich sketch-ruler component library for Vue 3, targeting design tools, low-code platforms, and big-screen visualization. It includes a framework-agnostic core package (`@sketch-ruler/core`) with 2D transform engine, plugin system, snap engine, canvas manager, and minimap engine—all zero DOM dependencies. Separate packages handle canvas rendering (`@sketch-ruler/canvas`) with optimized label caching, offscreen caching, and input management (mouse, keyboard, wheel), and a selection engine (`@sketch-ruler/selecto`). The main Vue package (`vue3-sketch-ruler` / `@sketch-ruler/sketch-ruler`) provides Vue components (SketchRuler, Minimap, RulerLine) plus composables for canvas transform, ruler scale, and snap detection. The architecture is cleanly layered, well-tested with Vitest, and shipped via npm. The demo site showcases multiple use cases (editors, whiteboards, org charts, big-screen displays). The code demonstrates mature engineering with reusable patterns, though the large monorepo and external demo dependencies introduce some maintenance surface.
This repository is a semantic-release plugin that automates the publishing of npm packages. It implements four lifecycle steps: verifyConditions (validates configuration and authentication), prepare (updates package.json version and optionally creates a tarball), publish (publishes the package to the npm registry), and addChannel (adds a release to a dist-tag). The plugin supports both token-based authentication (via NPM_TOKEN) and OIDC-based trusted publishing for GitHub Actions, GitLab Pipelines, and CircleCI. It can publish to custom registries, handle scoped packages, and skip publishing for private packages or when npmPublish is false. The architecture is a set of exported async functions that receive pluginConfig and context from semantic-release, delegating to internal lib modules. External dependencies include the npm CLI (executed via execa), fs-extra for file operations, registry-auth-token for authentication, env-ci for CI provider detection, and @actions/core for OIDC token retrieval. The codebase is well-structured with clear separation of concerns, comprehensive error handling using AggregateError, and extensive test coverage with both unit and integration tests.
This repository is a Next.js library for Cloudinary integration, providing React components and utility functions for image/video optimization, uploads, and transformations. The library includes components like CldImage (Next.js Image wrapper), CldVideoPlayer, CldUploadButton/Widget, and CldOgImage, along with URL generation helpers. It supports both Pages and App Router, handles responsive images, placeholders, and Cloudinary-specific features like AI transformations. The architecture is modular with clear separation between components, helpers, loaders, and configuration. The library is actively maintained with semantic-release, comprehensive tests, and broad Next.js/React version support.
This repository is the official Helm chart collection for deploying Kong API Gateway and related operators (Kong Ingress Controller, Kong Gateway Operator, Kong Operator, Kong AI Gateway) on Kubernetes. It provides production-grade deployment templates with support for DB-less, PostgreSQL, hybrid mode, enterprise features, cert-manager integration, Prometheus monitoring, and admission webhooks. The architecture is a multi-chart Helm repository with subcharts for CRDs (kic-crds, gwapi-crds, ko-crds) and extensive CI snapshot testing via helm-chartsnap. Key entry points include the main `charts/kong/` chart for the gateway and ingress controller, `charts/kong-operator/` for the Kong Operator managing Konnect and AI gateway resources, and `charts/gateway-operator/` for the Gateway API operator. External dependencies include Kong container images, cert-manager, Bitnami PostgreSQL (optional), and Konnect SaaS for enterprise deployments. The repository is actively maintained with regular releases, changelogs, and upgrade guides, though CRDs are auto-generated and may drift from upstream operator versions.
The pywpsrpc repository provides Python bindings for the WPS Office RPC (Remote Procedure Call) interface, enabling automation of WPS Office applications (Writer, Presentation, Spreadsheets) on Linux. It allows Python scripts to create, edit, format, and convert documents, handle application events, and embed WPS Office windows in custom Qt/PySide2 applications. The library is structured into three main modules (rpcwpsapi, rpcwppapi, rpcetapi) corresponding to the three WPS Office applications, with shared utilities in the py/ directory. The bindings are generated using SIP from C++ interfaces, and the project includes a comprehensive test suite and example scripts demonstrating core functionality like document manipulation, formatting, and event handling.
rsql-jpa-specification is a library that translates RSQL (RESTful Search Query Language) queries into Spring Data JPA Specifications or QueryDSL Predicates. It supports complex queries including entity associations, JSONB fields (PostgreSQL), custom operators, property mapping, and sorting. The architecture consists of core parsing utilities (rsql-common), JPA-specific implementations (rsql-jpa), QueryDSL implementations (rsql-querydsl), and Spring Boot starters for easy integration. The library uses the visitor pattern for RSQL parsing and CriteriaBuilder/QueryDSL APIs to construct specifications and predicates.
go-instrument is a CLI tool that automatically instruments Go source files with OpenTelemetry trace spans. It parses Go AST, identifies functions that accept a `context.Context` parameter, and inserts span creation, defer, and optional error recording statements. It handles various edge cases: anonymous functions, build constraints (ignore/exclude), generated files, custom context/error parameter names, already-instrumented functions, and preserves original line numbers for panic stack traces via compiler directives. The tool is implemented as a reusable library with a clear separation between the generic AST processing engine (`processor` package) and the specific instrumentation strategy (`instrument` package), allowing custom instrumenters. The CLI frontend is minimal; the core logic is in the `processor` and `instrument` packages and is cleanly abstracted via an `Instrumenter` interface. The codebase is well-tested, includes fuzz testing, and uses current Go tooling.
Yet Another Surge Dashboard (YASD) is a React 19 single-page application for managing and monitoring Surge network proxy instances through their HTTP API. The application provides a web-based interface to configure Surge instances, view network traffic statistics, manage profiles and rules, and inspect request logs. Built with a modern tech stack including Vite, TypeScript, Redux Toolkit, SWR for data fetching, and shadcn/ui for components, it features internationalization (English/Chinese), mobile responsiveness, and PWA capabilities. The architecture follows React best practices with clear separation of concerns between components, hooks, state management, and API layers.
Prosopo is a privacy-focused, self-hosted CAPTCHA alternative that provides multiple challenge types—image selection, puzzle (image jigsaw), proof-of-work, and frictionless (behavioral bot detection). The system comprises an Express-based provider API (with MongoDB and Redis for persistence and caching), a CLI for administrative tasks, client-side embeddable widgets (vanilla JS bundle, React/Angular/Vue/Svelte wrappers), and a suite of supporting libraries for cryptography, locale, datasets, and native Rust modules (JA4 TLS fingerprinting, Merkle tree acceleration, puzzle rendering). Bot detection is multi-layered: client-side behavioral data (mouse/keyboard/touch events, SIMD readings) is collected and server-side scored, combined with JA4 TLS fingerprint analysis, IP reputation (ipapi.is + MaxMind), DNS asymmetry detection, spam email heuristics, and custom decision machines per site key. The architecture is a monorepo with ~70 workspaces, leveraging Vite for bundling, Vitest for unit/integration tests, and Cypress for E2E visual regression testing. The provider enforces access policies (allow/block/restrict) via a Redis-backed rules engine and maintains usage counters for rate limiting. Asset sealing (AES-256-GCM) protects image CDN URLs, and puzzle difficulty is sampled with a CSPRNG-stratified ladder to frustrate solver calibration.
django-auth-adfs is a Django authentication backend that enables integration with Microsoft ADFS and Azure AD for single sign-on (SSO). It implements OAuth2 and OpenID Connect flows to authenticate users against enterprise identity providers, automatically creating and updating Django users based on identity claims. The package provides Django authentication backends, middleware for enforcing authentication, URL handlers for the OAuth2 flow, and Django REST Framework integration for token-based API authentication. The architecture follows Django best practices with clear separation of concerns between configuration, backend logic, views, and middleware.
This repository is a Rust SDK/framework for building Redis modules, not an end-user application or data/research project. The workspace is organized as a library crate (`redis-module`) plus proc-macro helper crates (`redismodule-rs-macros`, `redismodule-rs-macros-internals`) that wrap the Redis Modules C API. Build code consumes vendored `redismodule.h` through `bindgen`, and the public API provides safe `Context`, `RedisKey`, `RedisString`, `RedisValue`, `RedisModuleIO`, configuration, key cursors, timers, blocking clients, thread-safe contexts, and command/info-handler registration. `redis_module!` and `#[command]` are the main module entry points; the included examples are small runnable modules, and integration tests spawn real `redis-server` processes to exercise them. Architecturally, the crate uses an unsafe FFI layer (`src/raw.rs`) underneath higher-level modules (`src/context/`, `src/key.rs`, `src/configuration.rs`, `src/io.rs`), and uses `linkme::distributed_slice` plus procedural macros to collect command, event, info, and defrag handlers. API-version compatibility is handled by feature flags (`min-redis-compatibility-version-6-0` through `8-0`) with a manual mapping table in `redismodule-rs-macros-internals/src/api_versions.rs`. The vendored C header includes Redis Labs / BigRedis extensions, reflecting production use inside Redis Enterprise modules. External build dependencies include `bindgen`, `cc`, libclang, and a Redis-compatible server for tests. The codebase is well structured for a low-level FFI SDK and contains several genuinely reusable patterns, but it has meaningful caveats: generated bindings are not committed, `bindgen` is pinned to an old version, the manual API-version table must be kept in sync as Redis evolves, and the FFI layer is necessarily large and unsafe. Overall it is an actively maintained, professional-quality SDK with a few deprecated APIs and some fragility around version-gated calls.
Specinfra is a Ruby library that provides a common layer for infrastructure testing tools like serverspec and itamae. It offers a unified interface to check system properties (packages, services, files, network configuration, etc.) across diverse operating systems and execution environments. The architecture features a clean separation of concerns: backend abstractions for different execution methods (local, SSH, Docker, WinRM, etc.), a command factory for OS-specific command generation, and modular helpers for system detection and property management. The library dynamically selects the appropriate implementation based on the target system's OS and version, then executes checks via the chosen backend. Key entry points include the main Specinfra module, the Backend system, and the CommandFactory, which together enable extensible infrastructure verification.
This is a VS Code extension that provides language support for the Crystal programming language. It offers syntax highlighting, code snippets, formatting, hover information showing types, jump-to-definition, problem detection, symbol navigation, macro expansion viewing, and test integration. The extension interacts with the Crystal compiler and shards package manager through CLI tools to provide these features. The architecture is modular with separate TypeScript files handling different concerns (completion, definitions, hover, formatting, tasks, etc.), coordinated through a main extension.ts file. It uses a mutex to prevent concurrent compiler tool usage and properly handles error cases and platform differences.
This repository is the official Mollie API client for Node.js (TypeScript), providing a typed SDK for integrating with the Mollie payment platform. It exposes a factory function `createMollieClient()` that returns an object with resource binders (e.g., `payments`, `orders`, `customers`, `refunds`, `settlements`), each offering CRUD operations and additional actions like cancellation or refunding. The architecture follows a clean layered design: resource-specific binders delegate to a shared `TransformingNetworkClient` that handles HTTP requests, response transformation, pagination, idempotency keys, retries, and throttling. Data models are separated into raw API interfaces and sealed helper-enriched types, with embedded/linked resource access abstracted through helper classes. The SDK supports both API key and OAuth authentication, callback-style and Promise-based APIs, and includes extensive test suites (unit, integration, and cross-runtime compatibility for Node, Bun, and Deno). The codebase is well-structured, uses modern TypeScript features, and includes a custom iteration API for paginated resources. Notable internal patterns include a generic Binder base class, parameter default injection, a throttling utility, and a rich set of type utilities (Maybe, Nullable, Seal, Xor).
This repository provides a comprehensive continuous integration (CI) solution for ROS (Robot Operating System) projects. It automates the process of setting up a ROS environment, building code, running tests, and performing additional checks (such as code formatting, static analysis, and ABI compatibility) across multiple CI platforms including Travis CI, GitLab CI, GitHub Actions, and Bitbucket Pipelines. The system is designed to be highly configurable, supporting a wide range of ROS distributions from legacy versions to the latest releases, and isolates builds using Docker by default to ensure consistency across different environments. The architecture is modular, with clear separation of concerns: entry points for each CI system delegate to a central orchestration script (ci_main.sh), which in turn relies on specialized modules for environment setup, ROS configuration, workspace management, and various build systems (catkin_make, catkin_tools, colcon, etc.). Notable for their reusability and craftsmanship are the utility library (src/util.sh), which provides robust logging, error handling, and timing functions, and the Docker isolation layer (src/isolation/docker.sh), which handles the complexities of running CI jobs in containers including volume mounting, credential forwarding, and container lifecycle management. The project demonstrates strong engineering practices through its maintainability, active support for both ROS1 and ROS2, and adaptability to various CI systems. It has been widely adopted in the ROS community, as evidenced by its usage in numerous repositories. Technical debt is kept low through regular updates to support new ROS distributions and CI platforms, and the codebase avoids common pitfalls in shell scripting by using well-structured functions and consistent error handling.
dpScreenOCR is a cross-platform desktop application for recognizing text from a selected screen region. It is built in C++ using the Tesseract OCR engine and Qt 5/6 for the graphical interface. The application runs as a system-tray utility: the user triggers a screen selection via a global hotkey, captures a portion of the screen, processes the image (grayscale conversion, upscaling, unsharp masking), and feeds it to Tesseract. Recognized text can be copied to the clipboard, added to a persistent history, or passed to an external executable. The architecture is modular, with separate libraries for OCR (dpso_ocr), system interaction (dpso_sys), image processing (dpso_img), network requests (dpso_net), sound playback (dpso_sound), configuration and history (dpso_ext), and a suite of cross-platform utilities (dpso_utils). Each module exposes a C API for C/C++ interoperability and includes platform-specific backends for X11 and Windows. The Qt UI provides a main window with recognition controls, a language manager for installing/updating Tesseract language packs, and export functionality for history. The project also packages a built-in gettext-compatible internationalization library (dp_intl) and supports 16 languages through Weblate. This is a pure application repository with no data analysis or machine learning training components. The code demonstrates solid engineering practices: clear separation of concerns, RAII resource management, comprehensive error handling, and an extensive CMake-based build system supporting multiple packaging formats (Unix bundle, Windows MSIX, Inno Setup). The test suite covers utility functions, geometry, SHA-256, version comparison, and platform-specific components, though the OCR pipeline itself has limited direct unit tests.
zlFetch is a lightweight JavaScript library that wraps the native Fetch API with quality-of-life improvements. It automatically parses response bodies based on `Content-Type` (JSON, text, form-urlencoded, NDJSON, Blob), provides promise-based error handling that rejects on 4xx/5xx status codes, supports request aborting, and includes shorthand methods for GET, POST, PUT, PATCH, DELETE. The library also offers streaming capabilities (SSE, NDJSON, chunked transfer), an EventSource wrapper for server-sent events, query string helpers, authorization header helpers, and a `createZlFetch` factory for pre-configured instances. The code is modular, well-typed with JSDoc, and thoroughly tested across browser and Node.js environments using vitest.
Org-fc is a spaced repetition system implemented as an Emacs package for org-mode. It allows users to mark org-mode headlines as flashcards and review them using spaced repetition algorithms (SM2 or FSRS). The system features multiple card types (normal, double, text-input, cloze, vocab), efficient indexing via AWK scripts with caching, a dashboard for statistics, and optional extensions like audio playback and key-binding hints. The architecture is modular with clear separation between core functionality, review logic, card types, spacing algorithms, and utilities.