Harness Gitness is an open-source DevOps platform that provides Git hosting, CI/CD pipelines, artifact registries, and cloud development environments (Gitspaces). The system is built as a monolithic Go backend with a React/TypeScript frontend, using Google Wire for dependency injection and supporting both PostgreSQL and SQLite databases. Key entry points include the main server binary (`cmd/gitness`), REST API handlers organized by resource (repos, pull requests, spaces, pipelines, gitspaces, registries), and a CLI for administrative tasks. The architecture follows a layered pattern: HTTP handlers → controllers → services → stores, with an event-driven subsystem for asynchronous processing (pull requests, checks, gitspace lifecycle, merge queues). External dependencies include Drone runner libraries for pipeline execution, Docker API for container orchestration, and cloud provider SDKs (AWS, GCP) for infrastructure provisioning. The artifact registry is based on a fork of Harbor and supports OCI, Maven, npm, NuGet, Python, Helm, RPM, and other package formats. The frontend is modular, with separate codebases for the core Git UI, artifact registry (AR), and CDE (Gitspaces), using Harness UI components and custom factories for extensible package-type rendering.
Medusa is a headless commerce platform built as a modular monorepo. It provides a comprehensive backend with REST APIs for admin and storefront operations, a React-based admin dashboard, a workflow engine for orchestrating business processes (orders, returns, claims, etc.), and a plugin system for extending functionality. The architecture is domain-driven: each commerce domain (cart, order, product, pricing, payment, fulfillment, inventory, tax, promotion, customer, region, etc.) is an independent module with its own models, migrations, services, and workflows. The admin dashboard is a React SPA using TanStack Query, react-hook-form, and a custom data grid with virtual cells and clipboard support. The platform relies on PostgreSQL (via MikroORM) and optionally Redis for caching and workflow execution. It includes a design system with SVG icons and UI components, a JS SDK for client-side integration, and extensive documentation sites built with Next.js. The monorepo also contains CLI tools for project scaffolding, code generation, and API reference generation.
The Motion repository is a comprehensive library for creating complex animations and interactions for JavaScript, React, and Vue applications. It supports various features such as animation sequencing, spring animations, layout animations, gesture handling, and scroll-linked animations. The library is actively maintained, with a large number of commits and updates in the changelogs. The code is well-structured, and several reusable components and patterns are demonstrated in the examples.
InfluxDB 3 Core (IOx) is a production-grade, open-source time-series database written in Rust. It ingests data via line protocol (HTTP/gRPC), stores it in Apache Parquet on object storage (S3, Azure, GCP, local), and serves queries via SQL (DataFusion), InfluxQL, and FlightSQL. The architecture is a single binary (`influxdb3`) that combines an HTTP server (port 8181), gRPC FlightSQL endpoint, CLI, and an embedded Python processing engine for plugin-based triggers. The system is designed for low-latency last-value queries, high-throughput writes, and efficient columnar storage with catalog persistence as versioned binary logs and snapshots on object store. The codebase is a large Rust workspace (~40+ crates) with a clear separation of concerns: core libraries (`core/`) for query planning, Arrow utilities, authorization, and metrics; server crates (`influxdb3_*`) for catalog management, write buffering, processing engine, and system tables. Key entry points include `influxdb3/src/main.rs` (CLI), `influxdb3_server/src/unified_service/` (HTTP/gRPC routing), and `influxdb3_catalog/src/` (catalog operations). The query engine is built on a forked DataFusion with custom physical optimizers (gapfill, dedup, sort, union) and InfluxQL planning. External dependencies include object store backends, protobuf for gRPC, and Python (via PyO3) for plugins. The repository demonstrates high craftsmanship with several reusable patterns: a versioned binary record format for catalog persistence with forward-compatibility guarantees, a hook-based cache system with S3-FIFO eviction, a generic copy-on-write repository pattern, and a run-optimized merge sort for streaming sorted data. However, the large workspace, forked DataFusion pinned to a commit, and multiple catalog versions (v1–v4) introduce maintenance drift risks. The codebase is actively maintained with extensive tests, benchmarks, and CI/CD.
Headless UI is a library of completely unstyled, fully accessible UI components for React and Vue. It provides behavior-only primitives like Combobox, Listbox, Dialog, Popover, Tabs, RadioGroup, and Switch, with no built-in styling, allowing consumers to own the visual layer. The architecture is a monorepo with parallel React and Vue packages that share identical component APIs, test suites, and accessibility patterns, ensuring feature parity across frameworks. Components use render props (React) and slots (Vue) to expose state like open, active, selected, and disabled, plus an `as` prop for polymorphic rendering and a Transition component for enter/leave animations. The codebase is heavily tested with thousands of test cases covering keyboard navigation, focus management, ARIA attributes, form integration, and edge cases like dynamic children and virtual scrolling. Key entry points include the Combobox, Listbox, and Dialog components in both React and Vue, along with shared test utilities for accessibility assertions and interaction simulation. The library is actively maintained with a focus on accessibility-first design, headless composition, and cross-framework consistency.
The Vercel AI SDK is a comprehensive TypeScript monorepo providing a unified, provider-agnostic interface for building AI-powered applications. It abstracts interactions with dozens of LLM providers (OpenAI, Anthropic, Google, Mistral, Cohere, xAI, etc.) behind a consistent API for text generation, streaming, structured output, image/video generation, speech, transcription, embeddings, and tool calling. The architecture is modular: a core `ai` package exposes high-level functions (`generateText`, `streamText`, `generateImage`, `embed`, `transcribe`, `ToolLoopAgent`, `HarnessAgent`) and a middleware system, while separate `@ai-sdk/provider` packages define versioned model interfaces (v2–v4) and `@ai-sdk/provider-utils` provides shared utilities for schema validation, error handling, and HTTP. Each provider lives in its own package (e.g., `@ai-sdk/openai`, `@ai-sdk/anthropic`) with model-specific options and error handlers. The SDK also includes a harness/agent framework (`@ai-sdk/harness`) for integrating external coding agents (Claude Code, Codex, Cursor, GitHub Copilot, etc.) with sandboxed execution and workflow orchestration, plus UI integrations for React, Vue, Svelte, and Angular. Key data flows involve constructing prompts, calling provider APIs via fetch, streaming responses as Server-Sent Events or ReadableStreams, and transforming messages between model and UI formats. External dependencies include provider API endpoints, Zod for schema validation, and OpenTelemetry for telemetry.
This repository is a full-stack monorepo template for building SaaS applications using React 19, tRPC, and Cloudflare Workers. It features an edge-native architecture with three Workers (web router, app SPA, and API server) connected via service bindings. The template includes integrated authentication (Better Auth with email OTP, passkey, Google OAuth), multi-tenancy, Stripe billing, transactional emails (via Resend), file uploads to Cloudflare R2, and a Neon PostgreSQL database accessed through Drizzle ORM with Hyperdrive connection pooling. Key components include a reusable shadcn/ui component library, a typed WebSocket protocol package, and isolated database testing utilities.
DashBeam is a peer-to-peer encrypted file transfer application that operates without a central server. Built on the Iroh networking stack (QUIC, BLAKE3, relays), it enables direct device-to-device transfers with end-to-end encryption, NAT traversal via relays, and local LAN discovery via mDNS. The application is cross-platform, targeting desktop (Windows, macOS, Linux via Tauri), Android, and web (via a Rust WASM bridge). Its architecture cleanly separates a core protocol crate (P2P wire format, pairing, identity) from platform-specific I/O crates (native disk I/O for desktop/mobile, in-memory for web), all wrapped by a unified engine facade. The frontend is a modern React/TypeScript SPA with Zustand state management, a comprehensive UI component library built on Base UI, and 20+ locale translations. The system supports one-time share tickets, permanent device pairing, broadcast mode, transfer progress with resume, and self-hosted infrastructure. No telemetry or accounts are required, and the AGPL-3.0 license ensures openness.
This is the Microsoft FAST monorepo, a standards-based web component framework. It provides a lightweight, performant foundation for building custom elements with declarative templates, reactive data binding, server-side rendering (SSR), and hydration. The core library `@microsoft/fast-element` offers a complete runtime with observability, templating, dependency injection, and state management. Companion packages include a client-side router (`fast-router`), a test harness (`fast-test-harness`), and Rust-based build tools (`fast-build`, `fast-convert`) for SSR and template syntax conversion. The repository also contains example applications (CSR todo, SSR chat, WebUI todo), extensive Playwright integration tests, and a benchmark suite measuring rendering performance. The architecture is modular, with clear separation between runtime, build-time, and testing concerns. The codebase demonstrates high craftsmanship in areas like reactive observation, template compilation, hydration, and dependency injection, though some experimental features and cross-language (Rust/TypeScript) coordination introduce maintenance complexity.
GridStack.js is a production-grade TypeScript library for building responsive, drag-and-drop dashboard layouts. The core GridStack class manages widget lifecycle, DOM placement, responsive column switching, nested grids, serialization, and eventing, while GridStackEngine performs collision and positioning math without touching the DOM. The library ships its own drag-and-drop subsystem rather than depending on HTML5 drag-and-drop or jQuery, and it has zero runtime dependencies. Architecturally, the repository is a multi-package collection: a framework-agnostic core, a SCSS styling layer, and official Angular, React, and Vue wrappers. The wrappers integrate through callback hooks such as addRemoveCB, saveCB, and updateCB, plus DOM-stamped host APIs, allowing each framework to dynamically create and destroy widgets while keeping item content mounted during cross-grid drags. Demo applications under demo/, angular/projects/demo, react/src, and vue/src exercise the public API and serve as integration references. The project is actively maintained with a comprehensive Vitest and Playwright test suite, issue-numbered regression tests, and frequent releases. Its main technical debt is the large monolithic gridstack.ts (roughly 3100 lines) and the need to keep three framework wrappers synchronized with core API changes. The Angular wrapper is intentionally pinned to an older Angular major and some legacy build artifacts remain, but the core engine/UI separation, clean utility layer, and callback-based framework integration make many parts genuinely reusable.
Morphic is a self-hostable AI answer engine and chat application. In production it streams LLM research results into a rich chat UI: it runs an agentic researcher loop that calls search tools (SearXNG, Tavily, Brave, Exa, Firecrawl), fetches and extracts page content, allocates numbered citations, and emits a JSONL-based 'spec' stream that a generative UI renderer turns into structured cards, grids, headings, buttons, and inline images. Alongside the core chat it ships usage-budget metering, guest/anonymous chat, file uploads to S3-compatible storage, a notes/library feature, feedback collection, model discovery and selection, chat sharing, admin invitations, and an analytics relay that forwards scrubbed PostHog events without exposing authentication tokens.
This repository is a Next.js SEO library that provides React components for generating JSON-LD structured data (Schema.org) to enhance search engine optimization. The library offers over 50 specialized components for various Schema.org types (Article, Recipe, Product, Event, etc.) and a core JsonLdScript component for rendering JSON-LD tags. It includes utility processors for normalizing flexible input data into Schema.org-compliant formats and emphasizes security through XSS prevention in JSON-LD stringification. The architecture follows a modular component pattern with strong TypeScript typing, comprehensive testing (unit and E2E), and support for both Pages Router and App Router in Next.js. The library is actively maintained with recent updates, a changeset-based versioning system, and extensive documentation.
beautiful-react-hooks is a TypeScript library providing a collection of over 50 reusable, well-tested custom React hooks for common patterns such as lifecycle management, event handling (mouse, touch, swipe, drag, resize, scroll), geolocation, media queries, local/session storage, debounce/throttle, timers, animations, and more. The architecture is clean and modular: each hook is a standalone file with its own TypeScript types, unit tests, and documentation. Shared utilities (SSR detection, API support checks, warning helpers) are separated into a shared module, and a factory pattern is used to create storage hooks. The library supports tree-shaking via per-hook imports and provides both CommonJS and ES module builds. It also includes a comprehensive styleguidist documentation site with interactive examples. The code demonstrates strong engineering practices: proper handling of SSR, browser API availability checks, cleanup logic in useEffect, and memoization to avoid unnecessary re-renders. Peer dependencies (rxjs, react-router-dom) are required only for specific hooks, keeping the core lightweight.
This is a full-stack typing practice web application (keybr.com) built as a large TypeScript monorepo. The system provides adaptive typing lessons that track every keystroke, compute per-key statistics, and automatically generate lessons targeting the user's weakest keys. It supports dozens of keyboard layouts (QWERTY, Dvorak, Colemak, regional layouts, ergonomic layouts) and languages, with phonetic model-based word generation for practice text. The application includes a multiplayer typing race mode via WebSocket, user accounts with OAuth authentication (Google, Microsoft, Facebook), premium subscriptions via Paddle, and a theme designer for custom UI themes. The architecture is a monolith with server-side rendering (Fastr framework), a React 19 frontend bundled with webpack, a MySQL/SQLite database via Knex/Objection, and a separate WebSocket game server. The codebase is highly modular with over 50 packages covering UI widgets, charts, keyboard layout definitions, binary serialization, color science, math/statistics, internationalization, and code syntax generation for code-typing practice. While primarily an application, it also contains significant data/research components: phonetic model generation from word frequency dictionaries, statistical analysis of typing performance (learning rate, speed distributions, polynomial regression), and a C++ tool for validating user data files. The repository demonstrates high craftsmanship with clean abstractions, extensive test coverage, and reusable libraries that could be extracted for other projects.
Retrom is a self-hosted game library manager and emulation frontend that lets users manage their DRM-free game collection across devices. Its server component (Rust, gRPC, REST, WebDAV) handles library scanning, metadata enrichment (IGDB, Steam), cloud save synchronization (Ludusavi, WebDAV), and emulator configuration. The desktop client (Tauri) and web client (React, TanStack Router) provide a unified interface with both windowed and fullscreen modes, including in-browser emulation via EmulatorJS. The architecture follows a monorepo structure with well-separated packages for the database layer (Diesel/PostgreSQL), gRPC service handlers, UI components, and Tauri plugins, enabling reuse and independent development.
This repository is the frontend client suite for daily.dev, a developer-focused content and community platform. It is structured as a monorepo using pnpm workspaces, containing three primary packages: `packages/webapp` (Next.js application), `packages/extension` (browser extension), and `packages/shared` (shared UI components, hooks, and GraphQL logic). The system aggregates developer content, manages user profiles and communities (Squads), handles monetization (Plus subscriptions, Cores), and provides career opportunities. Key entry points include the Next.js pages router in `packages/webapp/pages` and the extension background/content scripts in `packages/extension/src`. Data flows primarily through GraphQL queries to an external `daily-api` service, with client-side state managed via TanStack Query and Jotai. External dependencies include Paddle for payments, GrowthBook for feature flags, and Cloudinary for media. The architecture emphasizes code sharing and consistency across platforms, with `packages/shared` serving as the core library for UI primitives, business logic, and API abstractions. The webapp utilizes Next.js for server-side rendering and static generation, while the extension leverages web extension APIs for browser integration. The codebase demonstrates strong engineering practices with strict TypeScript typing, comprehensive testing (Jest, Playwright), and a robust design system. However, the heavy reliance on feature flags and the use of a non-LTS Node version (v24.18) introduce some technical debt and potential compatibility risks. The platform supports multiple user journeys including content consumption, community engagement, and monetization. It features a sophisticated feed system with infinite scrolling, personalized recommendations, and content preferences. The extension provides companion features like new tab pages and frame embedding, requiring careful synchronization with the web app's authentication and permission models. The codebase is well-structured but complex, with deep nesting of contexts and modals that could impact maintainability if not carefully managed.
ReinaManager is a desktop application for managing visual novel game libraries, built with Tauri 2 (Rust backend) and React 18 (TypeScript frontend). It provides a comprehensive suite of features including game metadata aggregation from multiple sources (VNDB, Bangumi, Hikarinagi, DLsite, ErogameScape, YMGal, Kungal), game launch and process monitoring with playtime tracking, save data backup/restore, a download and installation pipeline, collection management with drag-and-drop, and cloud synchronization of play status. The architecture follows a clean separation between frontend and backend: the React frontend communicates via typed Tauri IPC through a service layer, while the Rust backend uses SeaORM with SQLite for persistence. The metadata system employs a source adapter pattern for extensibility, and the application is cross-platform (Windows, Linux) with platform-specific optimizations for game launching and monitoring. The codebase is under active development with frequent releases and demonstrates strong engineering practices including a well-structured migration system, a standalone segmented download engine, and a robust OAuth flow.
This repository is a production-grade React calendar component library (`@ilamy/calendar`) designed as a lightweight (~13 KB gzipped) replacement for FullCalendar. It provides month, week, day, year, and agenda views with drag-and-drop, resource scheduling, RFC 5545 recurring events, iCal export, and internationalization. The core ships no CSS and relies on Tailwind CSS v4 with shadcn/ui tokens, making it themeable and tree-shakeable. Architecturally, the library follows a plugin-first pattern: the core implements a pluggable kernel (`IlamyPlugin` interface) that accepts opt-in plugins for recurrence, agenda, and drag-to-create. Each plugin contributes views, event transformations, mutation scopes, and UI slots through a runtime composer. The state management uses a single `CalendarProvider` context that composes four engine slices (config, navigation, data, interaction). The view system is built on two grid primitives (vertical-grid for time-based layouts, horizontal-grid for date-based layouts) that are shared across all views and test harnesses. The codebase demonstrates strong engineering discipline: a huge unit test suite (995+ tests) with regression pinning against issue numbers, deterministic Playwright E2E tests, a CI pipeline with lint/build/type-check/test gates, and agent-driven code review skills. However, there is some duplication of UI primitives between packages, and the dependency on a custom dayjs wrapper for timezone handling introduces fragility. The library is actively maintained with frequent releases and detailed changelogs.
This is the monorepo for Supabase, the open-source Firebase alternative built on PostgreSQL. The repository contains the complete Supabase platform including: (1) Studio - a Next.js-based management dashboard for database, auth, storage, and edge functions, (2) Docs - a Next.js documentation site with MDX content and search, (3) WWW - the main marketing website, (4) UI packages - shared React component libraries built on Radix UI and Tailwind CSS, (5) pg-meta - a TypeScript library for PostgreSQL metadata introspection, (6) ai-commands - AI/LLM integration tools, (7) Docker configurations for self-hosted deployments, and (8) numerous example applications demonstrating Supabase integrations. The architecture is a pnpm monorepo using Turbo for build orchestration. The codebase demonstrates sophisticated engineering patterns including: a custom SQL query builder with branded types for safe SQL composition (pg-meta), a comprehensive component library with design system tokens, real-time features via WebSockets, row-level security policy management, and a multi-tenant organization/project structure. The repository is actively maintained with recent commits and has strong community engagement (105k+ stars).
This repository provides 'Diagrams', a Python library that lets you define cloud system architecture diagrams as Python code. It renders diagrams using Graphviz, supporting a wide range of cloud providers (AWS, Azure, GCP, Kubernetes, etc.) through auto-generated node classes. The library includes a CLI tool to execute diagram scripts and a web-based playground (React/TypeScript) that runs the library in-browser via Pyodide, allowing interactive editing and export. The architecture is a library with a CLI entry point, plus a separate SPA playground. Key entry points are the `diagrams` CLI command and the `Diagram`/`Node` classes. External dependencies include Graphviz (system binary), Jinja2, and for the playground: Pyodide, @hpcc-js/wasm-graphviz, React, CodeMirror. The codebase is well-structured with a code generation pipeline for provider nodes, comprehensive testing, and a polished user experience.