gh-poi is a GitHub CLI extension that safely cleans up local branches by identifying those with merged or closed pull requests. The application features a layered architecture separating command-line parsing (cmd/), external command execution (conn/), and shared data models (shared/). Key functionality includes fetching branch information from git, checking PR status via GitHub CLI, evaluating branch deletability based on multiple factors (lock status, worktree state, uncommitted changes), and performing safe deletion with dry-run support. The tool handles complex scenarios like worktrees, detached HEAD states, and various remote configurations.
This repository provides a library of reusable VHDL IP cores for FPGA design, focusing on fixed-point arithmetic, basic building blocks (FIFOs, RAM, clock crossing), and interfaces (SPI, I2C, UART, AXI). Each component is parameterized, well-documented, and includes testbenches for verification. The library is designed for portability across FPGA toolchains and includes tutorials for integration with major tools like Vivado, Quartus, and others.
MinVer is a minimalist versioning tool for .NET projects that derives version numbers from Git tags according to SemVer 2.0. It operates as both an MSBuild package (MinVer) and a standalone CLI tool (minver-cli). The core logic in MinVer.Lib walks the Git commit history from the current HEAD backward to find the latest version tag. If the current commit is tagged, that version is used as-is; otherwise, it optionally increments the version (patch by default) and appends a height (number of commits since the last tag) as pre-release identifiers. The library handles tag prefixes, custom auto-increment strategies, minimum major/minor overrides, build metadata, and height suppression. The CLI tool wraps this logic with System.CommandLine argument parsing and environment variable support, while the MSBuild package integrates directly into the .NET build pipeline, setting standard version properties (AssemblyVersion, FileVersion, PackageVersion, etc.). The repository is well-organized with a clear separation between library, CLI, and build package, and includes extensive unit and integration tests that actually create Git repositories to verify behaviour. The code demonstrates high craftsmanship with async Git operations, clean error handling, and a modular design that makes the core versioning algorithm reusable.
Inngest JS is a TypeScript SDK for building reliable, event-driven applications with durable execution. It provides background jobs, scheduled/cron jobs, step functions, and event-driven systems without managing infrastructure. The SDK works across multiple runtimes (Node.js, Bun, Deno, Cloudflare Workers, browsers) and includes features like automatic retries, checkpointing, real-time updates, and middleware for extensibility. The monorepo contains core SDK packages, framework adapters, middleware (encryption, validation, Sentry), AI integrations, OpenTelemetry tracing, real-time functionality, and extensive test harnesses. Examples demonstrate integration with popular frameworks like Next.js, Express, SvelteKit, Remix, and NestJS.
Logflare is a production-grade, multi-tenant log management platform (now part of Supabase) built with Elixir/Phoenix. It ingests logs via HTTP, gRPC (OTLP), WebSockets, and platform-specific drains, processes them through a rule engine, and routes them to user-configured backends including BigQuery, ClickHouse, Postgres, S3, and many more. The architecture is a monolithic Elixir application with internal subsystems: an ETS-backed ingest queue for high troughput, Broadway pipelines for batched ingestion, a behaviour-driven adaptor system for pluggable storage backends, a custom query languagte (LQL) with a parser and dialect transformers, a distributed cache layer via Cachex and WAL busting, and Rust NIFs for performance-critial mapping and Arrow IPC. It includes a full web UI (Phoenix LiveView), a REST API (OpenAPI-documented), billing with Stripe, team management, and alerting. The codebase is largte (1700+ files) and mature (100+ database migrations), with extensive test coverage, benchmarks, and CI/CD pipelines. While predominantly an application, it also exhibits data engineerig aspects with its focus on high-volume log ingstion, schema evolution, and query optimization.
TurboAPI is a high-performance web framework designed as a drop-in replacement for FastAPI. It achieves significant performance improvements (7-22x faster according to benchmarks) by integrating a Zig-based HTTP core (turbonet) while maintaining full API compatibility. The framework uses a hybrid architecture where application logic remains in Python but network I/O, request parsing, validation, and optionally database operations are handled by Zig components. Key features include FastAPI-compatible routing and dependency injection, middleware support, WebSocket capabilities, OpenAPI automatic generation, and optional zero-Python execution paths for maximum performance. The project includes several reusable Zig libraries: dhi (validation), pg.zig (PostgreSQL client), metrics collection, and a high-performance radix trie router.
This repository contains `clojure-mode`, an Emacs major mode for editing Clojure, ClojureScript, and related languages. The system provides syntax highlighting (font-lock), indentation, navigation, and a suite of refactoring commands directly in the editor. The architecture is a single large Emacs Lisp file (`clojure-mode.el`) with an additional extra font-locking package. It defines a base `clojure-mode` derived from `prog-mode`, plus derived modes for ClojureScript, ClojureC, ClojureDart, Joker, Jank, and EDN data files. Key entry points are the mode activation functions and interactive commands like `clojure-align`, `clojure-thread`, `clojure-cycle-privacy`, etc. The indentation engine uses a backtracking algorithm that walks up the sexp tree to apply contextual indent specs (shared with `clojure-ts-mode`). Font-locking is regex-based and extensible, with special handling for docstrings, discard macros, and character literals. The package depends only on standard Emacs libraries (`cl-lib`, `imenu`, `align`, `subr-x`) and requires Emacs 27.1+.
The time-machine library is a Python package designed to mock system time in tests by patching the datetime and time modules at the C level. It provides a versatile API that can be used as a context manager, decorator, or pytest fixture, allowing developers to set a fixed time or simulate time progression. The library supports timezone handling, nesting of time travel contexts, and an escape hatch to access the real time when needed. Additionally, it includes a command-line tool to assist in migrating from the popular freezegun library. The core innovation lies in the C extension (_time_machine.c), which directly manipulates the function pointers of the datetime and time modules to replace them with custom implementations. This approach ensures high performance and comprehensive mocking, affecting all references to these functions throughout the Python process. The Python layer manages the state of active time travels, handles timezone settings via the TZ environment variable, and provides a rich set of features for controlling the simulated time, such as moving to different timestamps or shifting by a delta. The project demonstrates strong engineering practices with comprehensive test coverage, modern development tooling (including pre-commit hooks, linting, and type checking), and careful consideration of cross-platform compatibility. It maintains backward compatibility while introducing improvements, such as making the dateutil dependency optional and adding controls for interpreting naive datetime values. The CLI tool for migration showcases a practical use of the tokenize_rt library for precise source code transformations, reflecting attention to real-world usability.
Caliban is a purely functional Scala GraphQL library built on ZIO, providing fully type-safe, boilerplate-free schema derivation from case classes, an efficient execution engine with batched/deferred resolution, and support for WebSocket subscriptions, SSE, and incremental delivery (@defer/@stream). It implements Apollo Federation (v1 and v2) with entity resolvers, tracing, and schema reporting. The library offers a type-safe client module for Scala.js and JVM, an sbt plugin for compile-time code generation from GraphQL schemas, and adapters for http4s, Akka HTTP, Pekko HTTP, Play, and ZIO HTTP. Interoperability is provided through Cats Effect, Monix, Tapir, and multiple JSON libraries (circe, zio-json, jsoniter, play-json). The repository includes extensive tests, JMH benchmarks, and Apollo compatibility tests. It is actively maintained and cross-compiled for Scala 2.13 and 3.
Usernetes is a tool for deploying Kubernetes clusters without requiring root privileges on the host, mitigating potential container-breakout vulnerabilities. It supports two deployment modes: Kubernetes-in-Docker (using rootless container engines like Docker, Podman, or nerdctl) and Kubernetes-in-Kubernetes (running as UserNS-enabled pods in an existing Kubernetes cluster). The architecture is modular, consisting of a container image packaging Kubernetes components, Docker Compose/Kubernetes manifests for orchestration, a Makefile for management tasks, and helper scripts for initialization and networking. Key features include automatic subnet assignment based on hostname hashes, container engine detection, and seamless integration with kubeadm for cluster bootstrap.
utest.h is a single-header unit testing framework for C and C++ that provides automatic test registration via constructor attributes, sophisticated assertion macros with expression tracking, and cross-platform support. The framework supports basic tests, fixture-based tests, and indexed/parameterized tests. It outputs results in both human-readable console format and machine-readable XML format. The implementation demonstrates high craftsmanship through its platform abstraction layer, memory-safe test registration system, and clever use of compiler-specific features to eliminate boilerplate. The core functionality is entirely self-contained within utest.h with no external dependencies beyond standard libraries.
This repository is the OpenConfig public YANG models repository, a collaborative effort by network operators to develop vendor-neutral YANG data models for managing network devices. It contains hundreds of YANG modules covering configuration and operational state for routing protocols (BGP, OSPF, ISIS, MPLS, Segment Routing), interfaces, ACLs, QoS, optical transport, platform components, security, telemetry, and more. The models follow consistent patterns: config/state separation, identity-based extensibility, and augmentation-based composition. The repository also includes CI workflows for validation (pyang, goyang, yanglint), documentation, and release management. While not an application with runtime code, it serves as a foundational schema library for network automation and telemetry systems. The codebase is well-maintained with active development, frequent revisions, and a formal release process.
This repository is a Laravel package that provides comprehensive geographical data (countries, states, cities, timezones, currencies, languages) and IP geolocation functionality. It implements a facade-based interface (`World::countries()`) and RESTful API endpoints (`/api/countries`, etc.) for accessing the data, which is stored in JSON files and seeded into database tables via Artisan commands. The package includes localization support for over 20 languages, configurable modules, caching mechanisms, and middleware for automatic locale and geolocation handling. The architecture follows Laravel conventions with service providers, controllers, models, migrations, and seeders, while employing an Action pattern to separate query logic, transformation, and business rules.
This repository provides a comprehensive collection of Arduino-compatible libraries and examples for developing applications with LilyGo LoRa-based development boards. It includes libraries for LoRa wireless communication (RadioLib), display interfaces (TFT_eSPI, GxEPD, U8g2), sensor integration (SensorLib), button handling (AceButton), GPS parsing (MicroNMEA), and power management. The architecture follows a modular library pattern with extensive example applications demonstrating various use cases like point-to-point LoRa communication, LoRaWAN nodes, GPS tracking, sensor data display, and remote control systems. The codebase demonstrates good software engineering practices with clear separation of concerns, hardware abstraction layers, and well-documented components.
This repository is a comprehensive, production-oriented algorithmic trading framework implemented in TypeScript. It is organized as a monorepo with six interdependent packages: `trading-signals` (100+ technical indicator implementations with streaming `add`/`replace` semantics, each verified against external reference data like Tulip Indicators and Skender.Stock.Indicators), `trading-strategies` (strategy base classes, concrete strategies such as SMA crossover, scalp, trailing stop, and a multi-indicator confluence strategy, plus a backtesting engine and report generators), `exchange` (abstract broker interface with real implementations for Alpaca and Trading212, including mock broker for backtesting, candle batching, WebSocket streaming, and a CLI tool), `messaging` (a Telegram bot for managing accounts, strategies, watches, and reports via multi-step wizards), `candles` (labeled historical candle datasets for testing), and `trading-signals-docs` (a Next.js documentation site with interactive indicator demos and a visual backtester). The architecture emphasizes clean separation between signal generation, strategy logic, broker execution, and user interface. The indicator library is the core asset, providing a consistent contract (`IndicatorSeries`, `TechnicalIndicator`, `TrendIndicator`) with rich signal detection and state rollback. The strategy framework supports live trading and backtesting via the same advice-execution pipeline. The project is actively maintained with CI/CD, mutation testing, and a well-defined broker integration template. While the codebase shows high craftsmanship in its indicator implementations and test patterns, the large number of indicators and hand-derived test fixtures introduce maintenance overhead, and the tight coupling to Telegram limits platform portability.
cdncheck is a Go library and CLI tool for identifying whether an IP address or domain belongs to a CDN, WAF, or cloud provider. It uses embedded CIDR range data (compiled from ASN, URL, and static CIDR sources) and efficient IP matching via the `bart` radix tree. The library provides a clean `Client` interface with methods like `CheckCDN`, `CheckCloud`, `CheckWAF`, and `CheckDomainWithFallback` that also resolve DNS and check CNAME suffixes. The CLI wraps this with input/output handling, filtering, and JSON output. The codebase is well-structured, with clear separation between core logic, data generation, and CLI runner. It is actively maintained by ProjectDiscovery and used in their security scanning ecosystem.
The Facebook FBOSS (Open Switching System) is a network operating system for data center switches. It provides a modular architecture with a central agent daemon that controls the switch hardware (via HALs like SAI and Broadcom), manages routing protocols (BGP, etc.), and offers telemetry via FSDB. The system includes a CLI for configuration, various services (QSFP, LED, fan, sensor), and extensive testing. Key entry points are the agent main (fboss/agent/Main.cpp), CLI main (fboss/cli/fboss2/Main.cpp), and service daemons. Data flows involve configuration pushing to hardware, telemetry publishing via FSDB, and packet processing by the ASIC.
The Dropbox SDK for Python is an official library providing programmatic access to the Dropbox API v2. It enables developers to perform file operations, manage sharing, handle team administration, and interact with Paper documents through a Python interface. The SDK employs a code generation approach using Stone IDL to maintain API specification consistency, with hand-written components handling cross-cutting concerns like authentication, session management, and request resilience. Architecturally, the library is structured as a importable package with clear separation between transport logic (session management), core request handling (including OAuth 2.0 token refresh and exponential backoff retry), and API-specific modules generated from specifications. Key features include automatic token refresh, connection pooling via shared sessions, Dropbox-specific content hash calculation for upload integrity, and comprehensive error handling. The SDK supports both user and team authentication scopes with proper scoping enforcement. The project demonstrates strong maintenance practices with automated CI/CD pipelines for testing, linting, and publishing to PyPI. A dedicated workflow keeps the SDK synchronized with Dropbox's API specifications through scheduled updates. While the majority of API interface code is generated, the manually maintained components exhibit robust engineering patterns suitable for reuse in other HTTP client implementations. The SDK targets developers building applications that integrate with Dropbox services, focusing on reliability, security, and ease of use.
This repository provides a comprehensive suite of GitHub Actions for automating Terraform and OpenTofu workflows in CI/CD pipelines. Each action (e.g., terraform-apply, terraform-plan, terraform-validate) is implemented as a standalone reusable workflow with standardized inputs, outputs, and Docker-based execution environments. The architecture features a common shell library (actions.sh) that handles tool installation, backend initialization, and shared utilities, while individual actions focus on specific operations like plan generation, state management, or pull request commenting. Key capabilities include version detection from multiple sources, backend fingerprinting for state identification, automated PR commenting with approval workflows, and support for both Terraform and OpenTofu. The project emphasizes reliability through extensive testing across versions and backends, with clear separation of concerns between action definitions, implementation logic, and documentation generation.
Kagome is a self-contained Japanese morphological analyzer written in pure Go. It provides tokenization with part-of-speech tagging, multiple segmentation modes (normal, search, extended), and dictionaries embedded in the binary for easy deployment. The system includes a CLI tool with subcommands (tokenize, server, lattice, sentence), a RESTful API server mode, WebAssembly support for browser use, and C library API for FFI integration with languages like Python and PHP. The architecture centers around a lattice-based Viterbi algorithm for tokenization, with clean separation between tokenizer logic, dictionary handling, filtering utilities, and interface layers.