This is the Supabase JavaScript SDK monorepo, providing isomorphic client libraries for Supabase backend services. It is a well-structured TypeScript monorepo managed with pnpm and Nx, containing six core packages: auth-js (authentication), postgrest-js (database queries via PostgREST), realtime-js (WebSocket-based realtime subscriptions), storage-js (file storage and vector index API), functions-js (edge function invocation), and the umbrella supabase-js package that combines them into a single `createClient()` entry point. The SDK supports multiple runtimes (Node.js, Deno, browsers, Bun, React Native, Cloudflare Workers) and includes optional OpenTelemetry tracing support. The codebase demonstrates high craftsmanship with extensive TypeScript generics for type-safe query building, fluent builder patterns, robust error handling hierarchies, and comprehensive integration tests against local Supabase infrastructure. It is actively maintained with frequent releases, automated CI/CD, and a strong focus on backward compatibility.
pgflow is a PostgreSQL/Supabase-native workflow orchestration engine for defining and executing typed DAGs as background jobs. The system is split into six coordinated packages: a PL/pgSQL core (pkgs/core) that implements the complete workflow state machine in the database — flows, steps, runs, step states, tasks, retries with exponential backoff, map/reduce fan-out, conditional step execution, skip-cascade propagation, and realtime event broadcasting — plus a type-safe TypeScript DSL (pkgs/dsl) for declaring flows with compile-time-enforced inputs/outputs, a Deno/edge worker runtime (pkgs/edge-worker) that consumes PGMQ messages and executes step handlers via platform adapters (Supabase vs. plain process), a realtime-subscription client library (pkgs/client), and a CLI (pkgs/cli) for scaffolding new Supabase projects. Execution relies on pgmq for task queues, pg_cron for stalled-task recovery and worker health, pg_net for HTTP worker invocation, supabase_vault for credentials, and Supabase Realtime for atomic state-transition broadcasts.
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 is the official Netlify CLI (netlify/cli), a comprehensive Node.js command-line tool for managing the Netlify platform. It provides commands for local development (`netlify dev`), deployment (`netlify deploy`), serverless and edge functions, environment variables, blobs (key-value store), database migrations (local Postgres via PGlite), log streaming, AI agents, and site configuration. The architecture follows a modular command pattern using Commander.js, with each major feature (deploy, dev, functions, etc.) in its own subdirectory. The codebase is well-structured with clear separation of commands, utilities, and libraries. It integrates deeply with Netlify's API and SDKs, and includes extensive integration tests with mock APIs and site builders. While the CLI is production-grade and actively maintained, it carries significant TypeScript type safety debt (hundreds of ESLint suppressions and `@ts-expect-error` comments), and some modules exhibit high complexity (e.g., the deploy command is a ~900-line file). Overall, it is a reliable tool with a strong feature set, but refactoring and type tightening would improve maintainability.