Plane is an open-source, self-hosted project management platform that provides issue tracking, sprint planning (cycles), modules, pages (wiki), views, analytics, and real-time collaborative editing. The repository is a monorepo containing a Django REST API backend with Celery workers, multiple React frontends (main web app, public space app, admin panel), and a Hocuspocus-based live collaboration server. The architecture follows a service-oriented pattern with shared packages for UI components, editor extensions, types, utilities, and state management via MobX. The codebase demonstrates strong engineering practices with a rich filter system, extensible permission model, and a clean exporter pattern, though it shows signs of ongoing migration from Next.js to React Router and some code duplication across apps.
CopilotKit is a comprehensive SDK and framework designed to integrate AI agents into user interfaces across web, mobile, and chat platforms. It functions as a middleware layer connecting frontend UI components (React, Vue, Angular) with backend agent frameworks (LangGraph, CrewAI, PydanticAI, etc.). The core value proposition lies in its ability to synchronize state between the agent and the UI, support generative UI (A2UI) for dynamic component rendering, and facilitate human-in-the-loop workflows. The repository is structured as a monorepo containing core runtime packages, framework-specific adapters, and an extensive suite of integration showcases. The architecture relies on a centralized runtime (`@copilotkit/runtime`) that handles agent connections via SSE and manages tool execution. Frontend interactions are managed through hooks (`useCopilotKit`, `useAgent`) that subscribe to the runtime. The codebase demonstrates a polyglot approach, supporting Python, TypeScript, Java, and C# backends alongside multiple frontend frameworks. While the core SDK is well-structured, the repository exhibits significant code duplication across its 20+ integration showcases, which serve as both documentation and regression tests.
Hasura GraphQL Engine is an open-source, metadata-driven GraphQL server that provides instant, real-time GraphQL APIs over multiple databases (PostgreSQL, MSSQL, BigQuery, CockroachDB, Citus, and custom sources via Data Connectors). The repository is a large monorepo containing a Rust-based v3 engine, a Go CLI for project management (migrations, metadata, seeds), a React/TypeScript admin console, and community boilerplates for authentication, event triggers, and remote schemas. The system exposes a single GraphQL endpoint that supports queries, mutations, subscriptions, streaming subscriptions, event triggers, cron triggers, remote joins, actions, and Apollo Federation. It relies on external databases, webhook endpoints for auth and event handling, and optionally OpenTelemetry collectors for observability. The architecture is modular: the v3 engine handles metadata resolution, GraphQL schema generation, and execution planning; the CLI manages project lifecycle; and the console provides a GUI for configuration. The codebase is actively maintained with frequent releases, but shows signs of technical drift due to legacy frontend code (Redux vs React Query), dual version support (v2/v3), and multiple programming languages (Rust, Go, TypeScript, Haskell, Python).
Sequelize is a mature, promise-based Node.js ORM supporting PostgreSQL, MySQL, MariaDB, SQLite, Microsoft SQL Server, DB2, IBM i, Oracle, and Snowflake. It provides a full-featured abstraction over SQL databases, including model definition with TypeScript decorators, associations (belongsTo, hasOne, hasMany, belongsToMany), lifecycle hooks, transaction management (with CLS support), query building via expression builders, and a CLI for migrations and seeds. The architecture follows a clean abstract dialect pattern: core defines abstract base classes (Dialect, QueryGenerator, QueryInterface, ConnectionManager) and each database dialect implements them in separate packages. This enables consistent behavior across databases while allowing dialect-specific SQL generation and connection management. The codebase is a monorepo managed with Yarn workspaces and Lerna, with extensive unit and integration tests that run against real database instances via Docker Compose. Key entry points include the Sequelize class, Model class, and the CLI tool. Data flows from application code through model methods (e.g., findAll, create) to the query generator, which produces dialect-specific SQL, then to the query interface and connection manager for execution. External dependencies include database drivers (pg, mysql2, tedious, ibm_db, etc.), validator.js, and utility libraries. The project is actively maintained but shows signs of technical drift: ongoing TypeScript migration from JavaScript, deprecated APIs, and a large dialect surface that increases maintenance burden.
NativeScript is a mature, cross-platform mobile application framework that enables developers to build native iOS, Android, and visionOS apps using JavaScript, TypeScript, or Angular. The repository is structured as a monorepo containing the core runtime (`@nativescript/core`) with platform-abstracted UI components, styling engine, data binding, and application lifecycle management; dual build toolchains (`@nativescript/vite` and `@nativescript/webpack5`) with Hot Module Replacement (HMR) support; platform type definitions (`@nativescript/types-ios`, `@nativescript/types-android`); and native widget libraries (Android Java, iOS Objective-C). The architecture is component-based: XML-declared UIs are parsed by a builder, instantiate native views, and styled via a custom CSS engine with selector matching, inheritance, and animations. An extensible property system with coercion, CSS properties, and change tracking drives reactivity. HMR infrastructure includes a Vite plugin that serves modules over WebSocket with framework-specific strategies (Angular, Vue, Solid, TypeScript). The codebase is heavily tested with unit tests (Vitest), platform-specific integration tests, and Appium E2E tests. Reusable design patterns include the observable data binding, property change origin tracking, platform-qualified file resolution, and CSS media query parsing. Notable technical drift risks include the coexistence of two build systems (webpack5 deprecated in favor of Vite), extensive platform-specific code duplication (`.android.ts`/`.ios.ts` pairs), and reliance on some deprecated iOS APIs in type declarations. Overall, it is a well-engineered framework with a large ecosystem and active development.
A monorepo providing `@pixiv/three-vrm`, a library for loading, controlling, and rendering VRM (Virtual Reality Model) avatars in three.js. It implements VRM 1.0 and partial VRM 0.0 specifications, handling humanoid bone mapping, facial expressions, eye gaze control (lookAt), first-person mesh culling, spring bone physics simulation, node constraints (aim, roll, rotation), and MToon toon material rendering. The library is structured as a collection of GLTFLoader plugins that parse VRM extensions from `.vrm` files. Core modules include `VRMLoaderPlugin` (orchestrating sub-plugins), `VRMCore` (humanoid, expressions, lookAt, firstPerson), `VRMSpringBoneManager` (verlet physics), `VRMNodeConstraintManager` (topological sort for constraints), and `MToonMaterial`/`MToonNodeMaterial` (custom shader/material for toon rendering). Both WebGL and experimental WebGPU renderers are supported. The codebase includes thorough examples, CI/CD, and compatibility shims for multiple three.js revisions (r123 through r180).
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.
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.
The Alfresco Content Application (ACA) is a production-quality Angular single-page application serving as the reference frontend for Alfresco Content Services (ACS). It provides enterprise content management capabilities including file/folder browsing, search with saved searches and faceted filters, document preview and versioning, sharing, favorites, trash management, library management, and folder-based automation rules. The application is built as an Nx monorepo with multiple distributable libraries (aca-content, aca-shared, aca-playwright-shared) and follows an extension architecture that allows plugins to add custom actions, evaluators, routes, and sidebar panels. State management is handled by NgRx, and the UI leverages Angular Material and the Alfresco Development Framework (ADF). Extensive end-to-end tests are implemented using Playwright, with shared page objects and API wrappers for maintainability. The codebase is actively maintained with frequent releases and a well-defined version matrix tracking compatibility with ADF, ACS, Node, and Angular versions.
Pollinations is a large monorepo hosting a multi-modal generative AI platform. It provides a unified API gateway (gen.pollinations.ai) for text, image, video, audio, 3D, and embeddings generation, routing requests to dozens of providers (OpenAI, Anthropic, Google, Fal, Replicate, ElevenLabs, etc.) with fallback chains, caching, rate limiting, and billing. A separate enterprise service (enter.pollinations.ai) handles authentication (GitHub OAuth, API keys, device code flow), user dashboards, API key management, Stripe/Pollen billing, community-hosted model endpoints, and a quest/reward gamification system. The platform also includes a design system UI library (@pollinations/ui), a Node.js SDK, a CLI tool (polli-cli), an MCP server, and over 20 community apps (chat, AI dungeon master, image reimagine, Discord bots, etc.). Infrastructure includes Cloudflare Workers, Durable Objects, D1, R2, Tinybird for analytics, and GPU inference servers (Flux, Dreamshaper, Z-Image) deployed on Vast/IO.net. The architecture is service-oriented within a monorepo: each major service (gen, enter, media, pollinations.ai) is a separate Cloudflare Worker with its own wrangler.toml and dependencies. Shared packages (shared/, packages/) provide cross-cutting concerns like billing logic, model registry, auth middleware, HTTP error handling, and UI components. Data flows from user requests through middleware (auth, balance, cache, rate-limit, safety, model resolution) to provider-specific adapters, with usage events published to Tinybird for analytics and billing. The system is heavily tested with Vitest, including integration tests with Cloudflare Workers test environment and VCR snapshots. External dependencies include Cloudflare (Workers, D1, R2, KV, Durable Objects, Vectorize), Tinybird (analytics), Stripe (payments), GitHub (OAuth, quests), and numerous AI model providers. The codebase is predominantly TypeScript with some Python (Floret agent, GPU servers, social automation) and Rust (polli-core for Discord bot). While the core platform is well-maintained, there is significant drift in community apps and infrastructure scripts, and the sheer number of provider integrations creates maintenance surface area.
Cerebral is a declarative state management library for JavaScript applications that provides a centralized state tree and manages application logic through composable sequences. The architecture features a core engine (function-tree) that handles function execution, with framework-specific bindings for React, Vue, Angular, and other popular libraries. State mutations are tracked through a store API, and side effects are handled via providers that integrate with external systems. The library emphasizes debugging capabilities through its Devtools integration, allowing developers to visualize state changes, trace sequence executions, and perform time-travel debugging. Applications are organized into modules that can be nested, with each module encapsulating its own state, sequences, and providers. Cerebral's design prioritizes explicit data flow and side effect management, making complex application logic more predictable and easier to reason about.
Ember Inspector is a browser extension (Chrome, Firefox, Opera, bookmarklet) that provides a rich debugging interface for Ember.js applications. It injects the `ember-debug` library into the target page, which collects runtime information about components, routes, data (Ember Data), promises, render performance, deprecations, and object internals. The inspector UI is an Ember.js application that communicates with the injected debug library via a message-passing port abstraction, using adapters specific to each browser environment. The codebase is a monorepo with four packages: `ember-debug` (injected debug library), `ember-inspector` (UI), and two test apps (classic and vite). It is actively maintained by the Ember core team, with CI/CD pipelines, extensive tests, and automated release planning. Architecture: The system is split into two halves. The `ember-debug` package uses a `Port` class for event-driven messaging and adapters (Chrome, Firefox, WebSocket, bookmarklet) to bridge the injected script to the extension's background page or devtools panel. The `ember-inspector` package is a full Ember app that renders tabs (Component Tree, Route Tree, Data, Promises, Deprecations, Render Performance, Info) and features an Object Inspector for drilling into property values and editing them. The UI uses a schema-based list rendering pattern, debounced search, and resizable/draggable columns. The object inspector handles both classic Ember objects and modern Glimmer components, including computed properties, tracked properties, getters, and services. Despite reliance on private Ember APIs and version-specific code paths, the codebase demonstrates strong engineering practices, with modular components that are potentially reusable (e.g., port messaging, adapter pattern, resizable columns, property display component).
This repository is a production full-stack application for browsing, searching, downloading, and publishing galgame (visual novel) sticker packs. It is a pnpm monorepo containing a Nuxt 4 SSR frontend (`apps/web`) and a Go Fiber v3 API (`apps/api`) backed by PostgreSQL. The API exposes both internal service endpoints and a public read-only OpenAPI "face" for sticker content, while integrating with external ecosystem services: an OAuth 2.0 identity provider (PKCE, httpOnly session cookies, BFF pattern), a centralized content-addressed image service, a catalog service for games/characters, and a community service for comments, notifications, and reactions. Deployment is Docker images to GHCR via Dokploy, with versioned SQL migrations and GitHub Actions CI building all images on push to the `svelte-kit` branch. The backend is well-layered: handlers own HTTP concerns, services contain business logic without importing Fiber, repositories use GORM, and repeated cross-service communication is isolated in reusable `pkg` clients. Noteworthy engineering includes batch hydration for pack covers/tags/authors, trigram GIN search over flattened multilingual text, cursor pagination for notifications, and RFC 9457 problem-detail error responses in the public API. The frontend is organized into feature modules and includes a race-condition-safe catalog picker, OAuth PKCE utilities, and server-side OG image generation. The codebase is maintained and technically current, though some operational risks remain: dual error dialects between internal and public APIs, silent degradation when optional upstream services are down, and a few hardcoded backfill mappings in one-time scripts.
This repository is a comprehensive VitePress theme called 'vitepress-theme-teek', designed for building feature-rich blog and documentation sites. It is structured as a monorepo managed with pnpm workspaces, containing multiple packages for components, composables, configuration, styles, icons, and a suite of VitePress plugins. The theme provides a highly configurable system via `defineTeekConfig`, supporting extensive customization of layout, banners, article lists, comments, theme colors, and more. It includes over 50 Vue components (e.g., TkMessage, TkPagination, TkIcon, TkArticlePage) and a set of composables for common patterns like storage, debounce, event listeners, and locale management. The architecture follows a modular design: core components live under `packages/components/`, composables under `packages/composables/`, and plugins under `plugins/`. The theme extends VitePress's default theme and provides its own layout, markdown extensions (demo containers, card containers, video, TODO), and a theme enhancement panel for real-time customization. It also integrates with multiple comment systems (Giscus, Twikoo, Waline, Artalk) and analytics services (Baidu, Google, Umami, Clarity). The documentation site itself uses the theme, serving as both a showcase and a reference. Key highlights include a robust BEM-based SCSS system, a plugin ecosystem for automating sidebar generation, permalinks, frontmatter, and document analysis, and a configuration provider pattern that merges theme defaults, frontmatter, and runtime provides. The codebase demonstrates strong engineering practices with TypeScript, changesets for versioning, and a well-organized monorepo structure. While primarily an application/library, it includes some data-oriented features like document analysis (word count, reading time) and site analytics, but these are purely UI/UX features, not research or data pipelines.
Packmind is a developer productivity platform that centralizes engineering standards and distributes them to AI coding agents. It solves the problem of scattered standards (in Slack, Notion, PR comments) that AI agents can't access and the manual copy-pasting of standards across repositories. The platform provides organization/space-based collaboration, Git provider integrations, LLM/AI service abstraction, marketplace for sharing components, deployment/target management, and change proposal workflows. It features a hexagonal architecture with clear separation of concerns across domains (accounts, organizations, spaces, standards, skills, commands, deployments), using NestJS for the backend, React for the frontend, and a separate CLI tool for local artifact management.
This repository is a modern, lightweight full-stack application template built with Turborepo. It consists of two main apps: a React single-page application (Vite + TanStack Router/Query/Form) for the frontend, and a Hono (Node.js) server providing an oRPC-based API with OpenAPI (Scalar) documentation. Authentication is handled by better-auth (email/password) with PostgreSQL via Drizzle ORM. The system supports CRUD operations for posts, includes dark/light theme toggling, and is fully containerized with Docker. The architecture follows a modular monorepo structure with shared packages for API contracts (oRPC), authentication, database schema and client, UI components (shadcn/ui), and reusable tooling configurations (ESLint, Prettier, Tailwind CSS, TypeScript). The codebase demonstrates strong engineering practices: environment variable validation with valibot, type-safe API contracts with oRPC, session-based auth with CORS, and a robust monorepo setup with Turborepo caching and dependency management.
This is a monorepo for 'pi', an AI coding assistant platform. The repository contains multiple packages including a coding agent with a terminal UI (TUI), multi-provider AI integration (OpenAI, Anthropic, Google, Bedrock, Mistral, xAI, and more), a durable execution framework for conversation persistence, a protocol layer with strict CBOR encoding, and telemetry infrastructure. The coding agent supports interactive mode with session management, tool orchestration, subagents, and MCP (Model Context Protocol) integration. The architecture is a TypeScript monorepo using npm workspaces with packages for AI providers, coding agent, durable execution, protocol, telemetry, and TUI components. The AI package provides a unified interface across multiple providers with OAuth flows, model catalogs, and streaming support. The coding agent implements a TUI with themes, keybindings, and interactive components. The durable package provides event-sourced storage with SQLite and JSONL backends, session management, and compaction. The repository also includes evaluation infrastructure (Docker-based evals), benchmarks for storage and delta traversal, and telemetry for usage tracking. The codebase demonstrates strong engineering practices with clean abstractions, reusable components, and comprehensive test coverage, though some areas (durable harness, experimental services) are still evolving.
Lion is a monorepo maintained by ING Bank that provides a comprehensive, white-label web component library built on LitElement. It focuses on accessible, performant, and extensible form controls (inputs, checkboxes, radio groups, selects, datepickers, IBAN, phone, file, etc.), overlays (dialog, tooltip, popover, drawer), navigation components (accordion, tabs, pagination, steps), and localization/internationalization utilities. The library is architected around a rich mixin system (e.g., FormControlMixin, ValidateMixin, OverlayMixin, LocalizeMixin) that allows deep customization without sacrificing encapsulation. It also includes Node.js tooling: an AST-based dependency analyzer (providence-analytics), a documentation publishing tool, and a Babel plugin for extending docs. The codebase demonstrates strong software engineering practices: extensive test suites, accessibility-first design, scoped custom element registries, and a modular export map. However, there are signs of technical drift (outdated dependencies like ESLint 8, TypeScript 4.9, Chai 4) and some duplicated code (e.g., localizeNamespaceLoader switch statements repeated across packages, translation drift). The monorepo uses changesets for versioning and has active CI/CD.
SushiSwap 2.0 is a multi-chain decentralized exchange (DEX) frontend built as a monorepo (pnpm, Turborepo) with Next.js App Router, React, and a shared UI library. It provides swap (simple, limit, DCA, TWAP), cross-chain swap (via LI.FI and Near Intents), perpetual futures (Hyperliquid-based), liquidity pools (V2/V3/Blade/Steer vaults), a token launchpad, staking (xSUSHI), and a developer portal (Zitadel auth, team management, API keys). The codebase supports EVM, SVM (Solana), Stellar, and Aptos chains, with namespace-aware wallet providers (Wagmi, Privy, Stellar Wallets Kit) and unified data fetching via TanStack Query and a custom GraphQL client. The architecture is heavily componentized, with reusable patterns like the Checker system (guards for connect/network/amounts), Provider composition (balance, price, trade state), and a design system in packages/ui. Testing includes Vitest unit tests and Playwright e2e with Anvil forks. The repo is actively maintained but carries moderate technical drift due to multi-chain duplication, hardcoded external API endpoints, and deprecated features (Blade pools, Arbitrum Nova minimization).
This is an enterprise-ready monorepo starter for content-driven websites, combining Strapi v5 (headless CMS) as the backend and Next.js 16 (App Router) as the frontend, managed with Turborepo and pnpm. In production, it provides a visual page builder with dynamic zones in Strapi, rendered server-side by Next.js with ISR and cache revalidation via Strapi document middleware. The system includes end-user authentication (Better Auth + Strapi JWT), localization (next-intl), media handling (imgproxy), SEO helpers, preview mode, optional CDN purge (Azure Front Door), and observability (Sentry, Azure Monitor). It is not a data research repository; the hybrid nature comes from data seeding workflows and Strapi config-sync exports that version content-model layouts and permissions, but the dominant character is a full-stack web application starter. The architecture is a monorepo with two primary apps (`apps/strapi` and `apps/ui`), shared packages (`packages/design-system`, `packages/logging`, `packages/eslint-config`, `packages/shared-data`, `packages/strapi-types`), a Docusaurus documentation site (`apps/docs`), and a Playwright QA workspace (`qa/tests/playwright`). Key entry points include the Strapi bootstrap and admin panel extensions, the Next.js middleware chain (`proxy.ts`) implementing basic auth, redirects, auth guard, and security headers, catch-all ISR pages, and API routes for revalidation, CDN purge, and Strapi proxying. The primary data flow is content authored in Strapi → published → document middleware triggers UI revalidation → Next.js fetches Strapi content via server-side API clients and renders pages with ISR. External dependencies are modern and pinned (Next.js 16, React 19, Strapi v5, TailwindCSS v4, Better Auth). The codebase demonstrates high craftsmanship with clean abstractions: a composable proxy middleware chain, pluggable CDN and telemetry providers, a typed Strapi API client with pagination, a hierarchy service computing fullPath changes with redirect compaction, and a shared logging package with OpenTelemetry correlation. Testing is comprehensive with Vitest unit tests and Playwright e2e/visual/SEO/accessibility suites. Some scaffolding remains incomplete (e.g., `removeThisWhenYouNeedMe` markers), and the two rich-text editors (CKEditor and TipTap) introduce duplicate rendering paths. Overall, this is a strong, well-documented starter suitable for teams building content-rich websites with a modern stack.