LobeHub/LobeChat is an open-source AI agent orchestration platform delivered as a full-stack monorepo. It provides a web SPA (Next.js), an Electron desktop application, a CLI tool, and a server backend. The system enables multi-model AI chat, agent definitions with built-in and MCP tool integration, user memory and knowledge bases, evaluation workflows, and acceptance testing. The architecture is modular with packages for model runtime, built-in tools, database (Drizzle ORM + PostgreSQL), prompts, and state management (Zustand). Key entry points include the Next.js app routes, tRPC routers for server-side logic, Hono API for agent execution and workflows, and the Electron main process for desktop features. Data flows involve user messages routed through an agent runtime that coordinates LLM providers, tool execution, and response streaming. External dependencies include PostgreSQL, Redis, S3-compatible storage, various LLM APIs, Upstash QStash for background workflows, and optional Elasticsearch for full-text search.
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.
Karakeep is a self-hostable bookmarking and read-it-later application. It supports saving links, notes, images, PDFs, and videos, with AI-powered auto-tagging, summarization, and semantic search. The system consists of a Next.js web app, an Expo React Native mobile app, a browser extension (Chrome/Firefox/Safari), a CLI, a Model Context Protocol (MCP) server, and a set of background workers (crawler, embeddings, feeds, webhooks, rule engine, backups). The backend uses tRPC for API, Drizzle ORM with SQLite, and a plugin system for swapping infrastructure (asset stores, queues, search, rate limiting). The architecture is monorepo with shared packages for types, server utilities, and React hooks. It is actively maintained with frequent releases and a large community.
Cal.diy is a fully open-source, MIT-licensed fork of Cal.com, providing a self-hostable scheduling platform. It is a large monorepo containing a Next.js web application (apps/web) for booking pages, settings, and admin, a NestJS API (apps/api/v2) for platform REST endpoints, and extensive packages for business logic (packages/features), integrations (packages/app-store with 50+ apps), embeddable booking widgets (packages/embeds), and reusable React atoms (packages/platform/atoms). The architecture uses tRPC for client-server communication, Prisma ORM with PostgreSQL, Redis caching, and a custom dependency injection system (ioctopus) alongside NestJS DI. Key patterns include a tasker abstraction for async/sync background jobs (webhooks, emails, calendar sync), a versioned webhook payload builder factory, repository pattern over Prisma, and a consistent app-store integration structure. The platform exposes a public API with OAuth2, webhooks, and embeddable components for third-party developers. The codebase is actively maintained with frequent schema migrations and CI/CD pipelines, but exhibits some technical drift due to dual API surfaces (tRPC vs REST), stub implementations for enterprise features, and generated files that require regeneration.
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 pnpm monorepo whose dominant application is apps/portal, a Next.js + tRPC + Prisma community platform for tech interview preparation. It delivers three interactive products: an anonymous salary/offer comparison tool with percentile analysis and currency conversion, a resume review system with PDF uploads, comments, stars and gamified badges, and a crowdsourced interview question bank with voting, full-text search and list curation. Authentication is NextAuth via GitHub, file uploads use Supabase storage, and all application logic is exposed through a tRPC router tree backed by PostgreSQL. apps/website is a Docusaurus static site that publishes the interview handbook content, blog posts and practice lists such as Grind 75; it is content-delivery rather than dynamic. The repo has some data/research flavour because it ships Prisma seed datasets (countries, states, companies, salary XLSX) and offer-analysis logic, but those are reference data and application features, not an analytical pipeline. The engineering follows T3 conventions: Zod-validated routers, React Hook Form, a custom UI kit and shared config packages. Strong reusable pieces include an accessible typeahead, a compound radio list, a currency exchange utility and an optimistic vote hook. Weaknesses are long and repetitive tRPC routers (especially the offers-profile update mutation), duplicated voting mutations across routers, inconsistent use of protected routers, hardcoded assumptions in seeds, and no visible automated test suite. The repository is actively maintained with recent commits and CI workflows, but it has medium technical drift: the portal pins older major versions of Next.js, tRPC and React Query, and it depends on a custom vite-plus toolchain. The Prisma schema has many 2022-era migrations and substantial complexity. It is best used as a reference architecture for building community-driven interview-prep features and as a source of isolated UI/utility patterns rather than as a drop-in application.
WeWe RSS is a monolithic NestJS application that provides RSS feed generation for WeChat public accounts (ĺžŽäżĄĺ Źäźĺˇ). It acts as a middleware between the WeRead (垎俥话䚌) platform and standard RSS readers. The system allows users to add WeChat public accounts via article links, fetches account metadata and article lists through the WeRead platform API, stores them in a MySQL or SQLite database, and exposes RSS/Atom/JSON feeds. It includes a cron-based scheduler for periodic feed updates, an admin dashboard built with React and NextUI, and supports features like full-text extraction, title filtering, and OPML export. The architecture is typical for a NestJS application: controllers handle HTTP requests, tRPC provides a type-safe API layer for the frontend, Prisma ORM manages database interactions, and the frontend is a separate Vite/React app. The codebase is straightforward and functional, with no standout reusable components that could be easily extracted without modification.
This repository is a large, personal competitive programming solution archive spanning multiple platforms (LeetCode, Codeforces, CSES, AtCoder, etc.) with a companion Next.js web application (LeetGoat) for managing and browsing problems. The codebase contains over 3,900 files, predominantly short algorithmic solution scripts in Python, C++, and JavaScript, accompanied by reusable algorithm templates and a structured problem metadata system using Prisma and Supabase. While the primary content is the solution library, the integrated web application provides authentication, admin CRUD for problems and tags, drill grouping, and practice pages. The app uses tRPC for type-safe APIs, Supabase for auth, and Prisma for database access. However, many site pages are placeholders ("Coming Soon"), indicating an early-stage product. Code quality varies widely: many solutions are well-commented and demonstrate strong algorithmic thinking (DP, segment trees, graph algorithms), while others are incomplete, contain known bugs, or carry disclaimers like "BAD SOLUTION". The templates directory contains genuinely reusable components (sparse tables, DSU, segment trees, centroid decomposition) that could be extracted for other projects. Maintenance is ongoing with frequent commit activity, but the sheer volume and mixed concerns (solutions + web app) introduce technical drift. No testing suite or CI is evident, and some solutions depend on external libraries (sortedcontainers) not always available in competitive programming environments.