zrok is a production-grade, self-hostable secure resource sharing platform built on OpenZiti overlay networking. It enables users to share web services, files, TCP/UDP tunnels, and VPN connections through firewalls and NAT without requiring inbound connectivity. The system supports both public and private sharing modes, OAuth authentication (GitHub, Google, OIDC), and includes a full REST API (v2), a CLI tool (`zrok2`), a React web console, a background agent daemon with gRPC remote control, and SDKs in Go, Python, and Node.js. Architecturally, zrok follows a controller-agent pattern. The controller is a Go REST server that manages accounts, environments, shares, accesses, frontends, namespaces, organizations, and bandwidth limits. It uses SQLite3 or PostgreSQL for persistence with versioned migrations, and integrates with InfluxDB for usage metrics and RabbitMQ (AMQP) for dynamic proxy mapping updates. The agent runs as a background process on the user's machine, managing child processes for each share/access and exposing a gRPC API for remote management. Frontend proxies (public, dynamic, socks, Caddy) handle incoming traffic with OAuth, basic auth, and interstitial pages. Key entry points include the CLI commands under `cmd/zrok2/` (e.g., `share`, `access`, `enable`, `admin`), the controller REST handlers in `controller/`, the agent gRPC service in `agent/agentGrpc/`, and the SDK packages in `sdk/golang/sdk`, `sdk/python/src/zrok2`, and `sdk/nodejs/sdk`. The system also includes a canary testing framework for continuous health validation and a comprehensive metrics/limits engine for bandwidth enforcement. External dependencies include OpenZiti (overlay network), InfluxDB (metrics), RabbitMQ (messaging), Caddy (optional web server), and various OAuth providers. The project is actively maintained with frequent commits, automated CI/CD, and multi-platform release pipelines (Linux, macOS, Windows, Docker).
Gophercloud is a comprehensive Go SDK for OpenStack cloud APIs. It provides typed client libraries for over 20 OpenStack services, including compute, networking, block storage, identity, load balancing, container orchestration, bare metal, DNS, key management, and more. The library handles authentication via Keystone (v2/v3), clouds.yaml, environment variables, or direct options, and includes a robust pagination framework (linked, marker, single page) used by all list operations. It follows consistent patterns: each resource has Create/Get/List/Update/Delete functions, builder interfaces for request options, and result types with Extract() methods. The codebase is heavily tested with both unit tests (HTTP mock fixtures) and acceptance tests (against real OpenStack deployments). While primarily a library for infrastructure management, it also exposes utilities like pointer helpers, JSON time parsing, and config file loading. The architecture is modular and extensible, with many reusable patterns.
This monorepo provides a comprehensive TypeScript SDK for the AT Protocol (Bluesky), including client libraries, server frameworks, OAuth authentication, identity resolution, data serialization (CBOR, CAR, CID), and lexicon-driven code generation. The architecture is modular, with ~50 packages organized by domain (clients, servers, utilities, definitions, OAuth, identity, bluesky-specific features). Key entry points include the generic XRPC client (`@atcute/client`), the OAuth browser and node clients, the XRPC server framework with WebSocket support, and the lexicon CLI for generating TypeScript bindings from AT Protocol schema definitions. Data flows involve typed API calls over HTTP/WebSocket, with automatic validation, rate limiting, and caching. External dependencies include `valibot` for runtime validation, `@noble/curves` for cryptography, and platform-specific WebSocket/Fetch implementations.
Screenshotbot is a comprehensive screenshot testing and visual regression tracking service built with Common Lisp. It provides a self-hostable platform that integrates with CI/CD systems to capture, compare, and report on screenshots from mobile and web tests. The system features a multi-tier architecture with a Lisp backend (using Hunchentoot), Bootstrap-based frontend, custom object persistence layer, and extensible plugin architecture for integrations with version control systems (GitHub, GitLab, etc.) and communication platforms (Slack, Email). Key components include SDKs for Android/Firebase integration, a Gradle plugin for Android builds, and a CLI tool for CI workflow integration. The platform includes user authentication, team management, role-based access control, audit logging, and a dashboard for visualizing test results.
This is the official JavaScript/TypeScript SDK for the Algorand blockchain, version 3.7.0. It provides a comprehensive set of tools for constructing, signing, encoding, and submitting transactions to Algorand nodes, as well as querying blockchain state via the Algod v2, Indexer, and KMD APIs. The SDK supports all transaction types (payment, asset management, application calls, key registration, state proofs, heartbeats), atomic transaction groups, ABI encoding/decoding for smart contract interactions, logic signatures (escrow, delegation, multisig), and post-quantum Falcon-1024 signatures. It is designed for both Node.js and browser environments, with CommonJS, ESM, and webpack bundle outputs. The architecture is modular: a core encoding layer (schema-based msgpack/JSON serialization) underpins all data types; a client layer abstracts HTTP communication with token-based authentication; a transaction builder pattern provides ergonomic construction; and a signer abstraction decouples signing logic from transaction assembly. Key entry points include the `Algodv2`, `Indexer`, and `Kmd` client classes, the `Transaction` class, `AtomicTransactionComposer` for atomic groups, and the `LogicSig`/`LogicSigAccount` classes. Data flows involve constructing transactions, signing them (via raw keys, multisig, or external signers), encoding to msgpack, and submitting to the network. The SDK also handles decoding of responses, including complex structures like block headers, state deltas, and simulation results. External dependencies include the `algorand-msgpack` package for msgpack encoding, `@algorandfoundation/falcon-wasm` for post-quantum signatures, and `hi-base32` for address encoding. The SDK is extensively tested with unit tests (Mocha), integration tests (Cucumber with mock servers), and browser tests (Selenium). It is actively maintained with regular releases, automated code generation from Algorand API specifications, and CI/CD pipelines for linting, testing, and publishing.
dockerode is a Node.js library that provides a comprehensive client for the Docker Engine API. It is architected around entity objects (Container, Image, Volume, Network, Service, Secret, Config, Plugin, Node, Task, Exec) that encapsulate the corresponding Docker API endpoints. The library relies on docker-modem for HTTP transport and supports both Unix sockets and TCP connections with TLS. It offers dual callback and Promise-based interfaces for all operations, allowing flexible integration patterns. A standout feature is its sophisticated stream handling. The library passes raw HTTP streams directly to the user, enabling advanced patterns like stream demultiplexing and piping. It supports HTTP connection hijacking for interactive exec and attach sessions, providing true bidirectional stdin/stdout/stderr communication. For modern Docker builds, it includes a BuildKit integration layer (lib/buildkit.js, lib/session.js) that transparently decodes protobuf status messages and handles gRPC session upgrades, demonstrating high craftsmanship in protocol handling. The codebase is actively maintained, with CI testing against Node.js 16 through 22. It has a comprehensive test suite covering containers, images, networks, volumes, services, and swarm operations. While it retains some legacy patterns (extensive use of var, dual callback/Promise APIs), the core architecture is clean, the reusable components are genuinely extractable, and the overall quality is strong. It is a mature, feature-rich SDK that faithfully implements the Docker Remote API.
The Dropbox SDK for JavaScript (dropbox-sdk-js) is a lightweight, promise-based client library that provides a programmatic interface to the Dropbox v2 API. It supports both Node.js and browser environments, with full OAuth 2.0/PKCE authentication, file upload and download with resumable and parallel streaming, exponential backoff retries, progress reporting, and content hash validation. The library is auto-generated from Dropbox's API specification (Stone) and exposes hundreds of endpoint methods covering files, sharing, team management, users, and more. It is designed for production use with robust error handling, rate-limit awareness, and environment-aware binary types. The codebase demonstrates strong architectural separation of concerns: authentication logic is encapsulated in `DropboxAuth`, file transfer logic in dedicated uploader/downloader classes, and API request routing in generated route definitions. The SDK is well-tested with unit, integration, and TypeScript type tests, and includes comprehensive examples for both browser and Node.js usage patterns.
This repository is the official open-source implementation of the Matter smart home connectivity standard, developed by the Connectivity Standards Alliance. It provides a comprehensive SDK for building Matter-compliant devices (e.g., lighting, locks, thermostats, sensors) and controllers (e.g., smartphone apps, hubs). The codebase is a large, multi-platform C++ project with a layered architecture: a data model layer defining over 100 clusters (OnOff, Temperature, DoorLock, etc.), an interaction model for read/write/execute/invoke, a transport layer supporting BLE, TCP, and UDP, a security layer for certificate-based attestation and encryption, and a platform abstraction layer for numerous embedded MCUs (ESP32, nRF, Silicon Labs, NXP, etc.) and operating systems (Linux, Android, iOS, Zephyr, FreeRTOS). The SDK includes example applications for device types, reference controller tools (chip-tool, darwin-framework-tool, Android/Kotlin controllers), and extensive test infrastructure. Key entry points are the example app main.cpp files, the chip-tool CLI, and the Python command-line tool. Primary data flows involve commissioning (pairing a device via BLE or network, then establishing secure IP communication) and ongoing cluster interactions (attribute reads/writes, command invocations, event subscriptions). The build system is GN (Google's ninja) with platform-specific overrides, and code generation via ZAP for cluster definitions. External dependencies include OpenThread, BoringSSL, mbedTLS, Pigweed, nlassert, and others. The project is actively maintained with frequent commits, but the sheer number of example apps and platform ports creates maintenance overhead and some duplication.
The Windows App SDK (formerly Project Reunion) is a Microsoft platform SDK for building modern Windows desktop applications. It provides a unified set of WinRT APIs and runtime components that bridge Win32 and UWP development, enabling features like app lifecycle management (single-instance, file/protocol activation), dynamic package dependencies (resolving framework packages at runtime), rich notifications (toast, push, badge), resource management via MRT Core (PRI files with qualifier-based selection), deployment APIs (package sets, validation), environment variable management, OAuth 2.0 authentication, and interop wrappers for storage pickers and camera capture. The architecture is modular: each feature area is implemented as a separate C++/WinRT component (DLL) that can be consumed individually via NuGet packages. The SDK supports both packaged (MSIX) and unpackaged (self-contained) apps, with a bootstrap DLL that initializes the runtime and hooks into the Windows package graph via Detours. Key entry points include MddBootstrapInitialize2 for runtime initialization, the WindowsAppRuntime DLL for COM class factories, and individual component APIs like AppNotificationManager, PushNotificationManager, and PackageDependency. External dependencies include the Windows SDK, C++/WinRT projections, the Windows Implementation Libraries (WIL), and Microsoft Detours for API interception. Data flows involve inter-process communication through shared memory (for activation redirection), named pipes (for OAuth callbacks), and COM out-of-process servers (for push notification long-running tasks). The codebase is heavily instrumented with TraceLogging telemetry and uses feature flags (TerminalVelocity) to gate experimental APIs.
stripe-node is the official Stripe API client library for Node.js and JavaScript runtimes. It provides a comprehensive, typed interface to the entire Stripe REST API (both V1 and V2), covering payments, billing, Connect, Treasury, Issuing, Terminal, and more. The library is auto-generated from Stripe's OpenAPI spec, ensuring tight alignment with the API surface. It supports multiple JavaScript runtimes (Node.js, Deno, Cloudflare Workers, browsers) via platform abstraction layers for HTTP, crypto, and event emission. Key architectural features include a pluggable HTTP client hierarchy (Node native, Fetch, custom endpoints), runtime type coercion for V2 decimal and int64 fields, robust error generation with typed error classes, automatic pagination with async iterators, and webhook signature verification. The codebase is well-tested with unit and integration tests across runtimes, and follows semantic versioning. While the vast majority of resource files are generated boilerplate, the core infrastructure (request sender, platform functions, crypto providers, auto-pagination) demonstrates solid engineering craftsmanship and is designed for extensibility.
Firecrawl is a production-grade web scraping, crawling, and structured data extraction platform designed to feed AI agents and LLMs with clean, markdown-formatted web data. The system exposes a multi-version REST API (v0, v1, v2) with endpoints for scraping single URLs, crawling entire sites, mapping site structures, searching the web, extracting structured JSON, monitoring page changes, and running autonomous AI agents. It supports multiple output formats including markdown, HTML, screenshots, PDF parsing, product/menu extraction, and branding detection. The architecture is a microservices-style monolith with a Node.js/Express API server at its core, backed by Redis for job queues and caching, PostgreSQL for persistent state, ClickHouse for analytics, Bigtable for job access logs, and GCS for blob storage. Background workers handle crawl orchestration, PDF processing, webhook delivery, and billing via RabbitMQ and FoundationDB queues. The platform integrates with external services for threat protection (Google Web Risk, Zscaler), billing (Autumn), search (SearXNG, DuckDuckGo, X Search), and LLM-based extraction (OpenAI, Anthropic). Nine official SDKs (Python, JavaScript/TypeScript, Go, Java, .NET, Ruby, PHP, Rust, Elixir) wrap the API with typed models, error handling, and async support, making it accessible across ecosystems. The codebase is extensive and well-tested, with over 2,000 files spanning controllers, scrapers, transformers, services, and utilities, but shows signs of technical drift through deprecated v0/v1 endpoints, multiple parallel implementations of similar logic (e.g., extract pipelines), and configuration sprawl across environment variables.
WxJava is a comprehensive Java SDK for the WeChat ecosystem, providing client libraries for Official Accounts (MP), Mini Programs (MiniApp), Enterprise WeChat (CP), WeChat Pay, Open Platform, Video Channels, and more. It is designed as a multi-module library to be embedded in Java applications, with first-class support for Spring Boot and Solon frameworks via auto-configuration starters. The SDK abstracts HTTP client backends (Apache, OkHttp, Jodd, HttpComponents), provides Redis-based config storage for distributed token management, and implements multi-tenant patterns for managing multiple WeChat accounts. It handles the full lifecycle of WeChat API integration: request signing, serialization (Gson/Jackson/XStream), message routing, and callback verification. The codebase is large and well-structured, though it shows signs of duplication across modules and mixed serialization frameworks, reflecting organic growth over time.
PMXT is a unified prediction market SDK that aggregates data and trading across 15+ venues (Polymarket, Kalshi, Limitless, etc.) into a single, consistent interface. The system provides a core TypeScript library with a local sidecar server (Express), plus TypeScript, Python, and CLI SDKs that support both self-hosted and hosted (trade.pmxt.dev) modes. It offers market data (events, order books, trades, OHLCV), WebSocket streaming, order management (create, cancel, fetch), account balance and positions, cross-venue router for event matching and arbitrage, and data feeds (Binance, Chainlink). The architecture is a monorepo with workspaces core, sdks/typescript, sdks/python, sdks/cli, and tools. Each exchange follows a clean fetcher → normalizer → error mapper pattern, and the SDK surfaces are partially generated from the core's method signatures. While primarily an application SDK, the project includes significant data normalization, cross-venue data aggregation, and a router for analytical queries, giving it a hybrid character.
This repository provides `mmx-cli`, a TypeScript-based command-line interface for the MiniMax AI platform. It allows users to authenticate, generate text, images, video, speech, perform web search, and manage configuration entirely from the terminal. The codebase is modular with a command registry pattern, supports both OAuth and API key authentication, handles streaming responses (SSE), and includes a programmatic SDK for Node.js/TypeScript consumers. Key architectural patterns include a hierarchical command resolution system, a generic HTTP client with retry and timeout logic, file download utilities with atomic writes, and a polling utility for async task monitoring. The CLI also automates setup for third-party AI coding agents (Claude Code, Codex, Grok, etc.) by writing configuration files. Testing is extensive with a mock server pattern. The tool is dual-region (global and China) with automatic endpoint detection. While early in development (version 0.0.0-dev), the engineering quality is solid with clear separation of concerns, typed error handling, and thoughtful output formatting (text, JSON). Some components like the agent configurator and video generation validation are tightly coupled to MiniMax-specific APIs, but many utility and client modules exhibit patterns reusable in other CLI tools or API wrappers.
Inlang is a localization platform that treats translation as code, storing messages in a versioned Lix database managed through Git. The monorepo includes a TypeScript SDK for loading, querying, and exporting translation projects; a CLI for running checks and machine translation; a plugin system for integrating with multiple message formats (JSON, ICU, i18next, Android XML, Apple xcstrings, and more); and Lit-based web components for editing translations in-browser. The SDK provides a rich data model (bundles, messages, variants with selectors) and a checks engine for detecting missing translations, unused messages, and plural errors. Architecturally, the repo is organized as a pnpm/Nx monorepo. The core `@inlang/sdk` package manages project lifecycle and database operations via Kysely. Plugins conform to a uniform `importFiles/exportFiles` interface and are loaded dynamically. The CLI uses Commander and Consola, while the UI components use Lit with Shoelace design tokens. The companion website (TanStack Start) serves documentation, a marketplace registry, and SEO-optimized pages. The system is designed to run in Node.js (CLI) and browsers (editor), with a focus on preserving file formatting through careful diffing and merging during export. Notable craftsmanship includes the `keepUnchangedJsonEntries` utility for byte-identical file preservation, the `EchoTracker` for optimistic UI state, the `pluralExamples` helper for locale-aware examples, and the `human-id` word lists for generating readable identifiers. These components are self-contained, well-tested, and reusable outside the localization domain. The codebase demonstrates strong engineering practices with extensive test coverage (vitest, Storybook, fuzzing) and compatibility tests ensuring backward compatibility across SDK versions.
This is the official Auth0 React SDK (`@auth0/auth0-react`), a client-side library that provides React bindings for Auth0 authentication. It wraps the core `@auth0/auth0-spa-js` library and exposes a React-friendly API via context, hooks, and higher-order components. The architecture follows a standard React context provider pattern: `Auth0Provider` wraps the application tree, and `useAuth0` (or `useAuth0Suspense`) provides authentication state and methods (login, logout, token management, MFA, passkeys). The SDK supports OAuth2 Authorization Code Grant with PKCE, refresh token rotation, DPoP, and custom token exchange. It is designed for single-page applications and is compatible with React 19+, including Next.js App Router (via `'use client'` directive injection). Key entry points include `Auth0Provider` (the root provider), `useAuth0` (primary hook), `useAuth0Suspense` (Suspense-enabled variant), `withAuthenticationRequired` (HOC for route protection), and `withAuth0` (legacy HOC). The SDK manages authentication state through a reducer (`src/reducer.tsx`) and provides a rich error hierarchy (`OAuthError`, `MfaRequiredError`, etc.). External dependencies are minimal: React, ReactDOM, and `@auth0/auth0-spa-js`. The codebase is well-tested with Jest unit tests (using a manual mock for the underlying SDK) and Cypress integration tests against a live Auth0 tenant. The SDK demonstrates strong engineering practices: typed interfaces, memoized context values, structured error handling, and a clear separation of concerns between the provider, hooks, and HOCs. It includes generated TypeDoc documentation and example applications for Vite, Gatsby, and Next.js. While the library is tightly coupled to the Auth0 ecosystem, its patterns (context-based auth, Suspense integration, error hierarchy) are reusable in other authentication contexts.
Stream Chat Swift is an iOS/macOS SDK for building real-time chat and messaging applications. It provides a modular architecture separating core networking (StreamChat), UI components (StreamChatUI), and shared utilities (StreamChatCommonUI). The SDK supports features like channels, messages, reactions, threads, polls, attachments, typing indicators, and presence. It uses Combine for reactive programming, Core Data for persistence, and WebSocket for real-time communication. The repository includes demo applications, example implementations (SlackClone, MessengerClone, etc.), and extensive testing infrastructure. The SDK follows protocol-oriented programming with dependency injection via Appearance and Components providers, enabling high customization.
@octokit/graphql.js is a lightweight, purpose-built JavaScript library for making GraphQL queries to the GitHub API. It wraps the `@octokit/request` HTTP client to handle authentication, variables, error parsing, and GitHub Enterprise Server base URL normalization. The primary entry point is the `graphql` function, which accepts a query string and optional parameters (variables, headers, operation name) and returns a promise of the response data. It also exposes a `withCustomRequest` factory for injecting a custom request instance, a `GraphqlResponseError` class for structured error handling, and a `withDefaults` method for creating pre-configured instances. The library is fully typed with TypeScript, supports ESM and bundling, and follows the Octokit ecosystem conventions. It does not handle pagination or subscription – it is purely a thin GraphQL client for the GitHub API.
Milvus Java SDK is a comprehensive client library for the Milvus vector database, supporting both legacy (v1) and modern (v2) APIs. It covers all core operations: collection/index/partition management, vector insert/upsert/delete/search/query, RBAC, resource groups, CDC, snapshots, and bulk import via Parquet/CSV/JSON files. The SDK uses gRPC for communication, includes connection pooling, schema caching, and iterator support for large result sets. A separate bulk writer module handles cloud storage uploads (S3, Azure, GCP) and import job orchestration. The codebase is professionally structured with a builder pattern for all request/response objects, extensive unit and integration tests, and examples demonstrating real-world usage. While dual API versions increase maintenance, the SDK is actively developed with a rapid release cadence aligned to Milvus server versions.
This is the LINE Messaging API SDK for Ruby (gem `line-bot-api`), a client library for building LINE bot applications. It provides auto-generated Ruby clients for LINE's various APIs (Messaging API, Webhook, Channel Access Token, Insight, LIFF, Manage Audience, Shop, Module, and Module Attach) from OpenAPI specifications. The library includes a webhook parser with constant-time signature verification, typed model classes with dynamic attribute support, and comprehensive RBS type signatures for static type checking. It is not a data research repository; it is a production-quality SDK maintained by LINE Corporation with active development, CI/CD pipelines, and example Sinatra applications.