Open Notebook is a self-hosted, AI-powered research assistant and knowledge management application. It allows users to collect sources (web pages, uploaded documents, text snippets), extract structured insights via LLM-driven transformations, organize content into notebooks, perform hybrid text/vector search, and generate AI podcasts with multi-speaker support using TTS models. The backend is built on Python with FastAPI and LangGraph for orchestration, SurrealDB for persistence (with a custom migration system), and the Esperanto library for multi-provider AI integration (OpenAI, Anthropic, Google, Ollama, and many others). The frontend is a modern Next.js application with React Query, i18n support for 14 locales, and a component library based on Radix UI/shadcn. The architecture follows a monolith-with-background-workers pattern: the FastAPI process handles both synchronous API requests and, via the surreal-commands library, asynchronous background jobs for content processing, embedding generation, and podcast generation. The codebase is well-structured with clear separation between API routers, domain models, utility modules, and frontend components. It exhibits strong security awareness—includes SSRF protection via DNS pinning, path containment for file uploads, Fernet encryption for stored credentials, and input validation throughout. The test suite is extensive (>100 test files) covering API endpoints, domain logic, error handling, and edge cases. There are some maintenance risks related to tight coupling with SurrealDB and the externally-maintained Esperanto/content-core/podcast-creator libraries, but overall the codebase is actively maintained and of professional quality.
Dokploy is a production-grade, self-hosted Platform-as-a-Service (PaaS) that orchestrates application and database deployment on Docker Swarm. The code confirms the README claims: it clones repos from Git providers (GitHub, GitLab, Bitbucket, Gitea), builds via multiple strategies (Dockerfile, Nixpacks, Railpack, Paketo, Heroku), provisions six database types (Postgres, MySQL, MariaDB, Mongo, Redis, LibSQL) as Swarm services, generates Traefik reverse-proxy configs with ACME/TLS and forward-auth middleware, runs rclone-based backups to S3-compatible storage, and streams logs/terminal/stats over WebSockets. It is not a research or data project; the only data assets are operational metrics collected by a Go agent into SQLite for monitoring dashboards.
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.
Polar is an open-source, full-stack monetization platform designed for AI-era software developers. It serves as a Merchant of Record, handling checkout flows, subscriptions, usage-based billing, seats, discounts, and global tax compliance. The system is built as a monorepo with a Python/FastAPI backend (async SQLAlchemy, Dramatiq workers, PostgreSQL, Redis, Tinybird for event analytics), a Next.js web dashboard and customer portal, a React Native mobile app (Expo), a design system (Orbit), and multiple SDKs (TypeScript, Python) with a CLI tool. Architecture follows a service-oriented pattern with versioned REST APIs (2026-04, 2026-10, 2027-01), a repository pattern for persistence, benefit fulfillment strategies for integrations (Discord, GitHub, Slack, license keys), and framework adapters (Next.js, Nuxt, TanStack Start, Better Auth) for easy integration. The platform also includes an internal backoffice (HTMX/tagflow), observability (SLOs, invariants, Prometheus metrics), and merchant migration tooling from Stripe.
This repository implements a self-hosted deployment platform alternative to services like Vercel or Netlify. It enables users to deploy GitHub repositories with zero-downtime updates, instant rollback, and preview deployments for branches. The platform provides team-based access control, custom domain support with automatic Let's Encrypt SSL, storage provisioning (databases/volumes), and real-time log aggregation via Loki. Built with FastAPI, SQLAlchemy, and ARQ for background jobs, the architecture separates concerns into routers, services, models, utilities, and workers. Infrastructure is orchestrated via Docker Compose, including Traefik for routing, PostgreSQL for primary data, Redis for caching/job queue, and Loki/Alloy for logs. Key entry points include the main FastAPI app, API routers for auth/project/team/admin, and worker entrypoints for ARQ jobs and deployment monitoring.
This repository implements a deep research assistant web application that combines large language models (LLMs) with web search capabilities to generate comprehensive research reports. Built with Next.js 15, React, and Tailwind CSS, it features a client-side interface for topic input and research workflow management, backed by API routes that proxy requests to external AI and search services to protect API keys. The system orchestrates an iterative research process: planning sub-queries, executing parallel searches across multiple providers (Tavily, Firecrawl, Exa, etc.), analyzing results with auto-review cycles, and generating cited final reports. Key architectural elements include Zustand-based state management with localForage persistence, a Model Context Protocol (MCP) server for standardized tool/resource exposure, PWA support for offline installation, and modular components for knowledge base management, file parsing, and real-time progress streaming via Server-Sent Events (SSE).
This is a monorepo for General Translation (GT), a comprehensive internationalization (i18n) and localization (l10n) platform. It provides runtime libraries for React, Next.js, Vue, React Native, Node.js, and Python frameworks, enabling developers to translate entire React components—not just strings—using a simple `<T>` wrapper. The platform includes a CLI for extracting translatable strings from source code, uploading them to a translation service, and downloading completed translations. A Babel/SWC compiler injects translation hashes at build time, and a Sanity CMS plugin manages document-level translations. The architecture is a multi-package monorepo with shared core types, a compiler pipeline, framework-specific adapters, and a cloud API client. The codebase demonstrates high craftsmanship with clean abstractions like condition stores, singleton caches, batch processing utilities, and a step-based workflow pattern. It is actively maintained with extensive test coverage and modern tooling (pnpm, Turborepo, TypeScript, Vitest).
SyntaxUI is a comprehensive documentation and showcase application built with Next.js 15, designed to display a library of pre-built React UI components. The application serves as both a marketing site and a functional reference for developers, allowing them to browse components, view live previews, and copy source code directly. It leverages the Next.js App Router for routing and server-side rendering, with MDX files used extensively for documentation content. The architecture is monolithic, centered around a static site generation approach with client-side interactivity for features like search and component previews. The core functionality revolves around displaying UI components categorized into buttons, loaders, text effects, and layout blocks. It integrates Tailwind CSS for styling, Framer Motion for animations, and Lucide React for iconography. The site includes a custom client-side search implementation using FlexSearch, which indexes the MDX documentation at build time. It also features dynamic elements like a GitHub stars counter and a Pro banner, managed via Zustand stores. The codebase is structured to separate the showcase components (in `src/showcase`) from the documentation pages (in `src/app/(docs)`), facilitating easy addition of new components. From a code quality perspective, the repository demonstrates strong engineering practices. It uses TypeScript throughout, ensuring type safety for components and utilities. The project utilizes modern Next.js features, including server actions for file reading and custom webpack loaders for search indexing. The separation of concerns is clear, with reusable UI primitives (like `ComponentPreview`) abstracted away from the specific component showcases. The documentation is generated from MDX, allowing for rich content embedding alongside code examples. The repository is actively maintained, evidenced by recent commits and a low number of open issues. It keeps pace with the ecosystem, utilizing the latest stable versions of Next.js and Tailwind CSS. There is minimal technical debt, with no deprecated APIs or outdated dependencies visible in the manifest. The code is clean, well-organized, and follows a consistent pattern, making it a valuable resource for engineers looking to build documentation sites or component libraries.
Open Dungeon is a fully local AI roleplay application that generates both narrative text and inline scene images on-device. Built as a Next.js 16 application with a React 19 frontend, it provides a rich interactive fiction experience where users can write actions, dialogue, or narration, and the AI narrator responds with streaming prose. The system supports multiple text backends: local Ollama models (Gemma 4 QAT variants) or any OpenAI-compatible server (LM Studio, llama.cpp, OpenRouter, etc.). Image generation is handled by a separate Python HTTP server that wraps optimized FLUX.2-klein backends (MFLUX/MLX on Apple Silicon, PyTorch SDNQ on CUDA/CPU) or an existing ComfyUI instance. The architecture is a monolith with a Next.js server handling API routes, SQLite for persistence, and an optional sidecar image server. Key entry points include the main chat UI (src/app/page.tsx), the story API (src/app/api/story/route.ts) which handles streaming narration, and the image generation API (src/app/api/images/route.ts). The codebase demonstrates strong engineering practices: thorough streaming support with artifact filtering, robust error handling with timeouts and fallbacks, clean database abstraction, and well-structured Python image server with resident model support.
SaaStart is a B2B SaaS starter kit built with Next.js and Auth0 that provides multi-tenancy organization management, user authentication/authorization, self-service SSO configuration (OIDC and SAML), security policy management (including MFA), user profile and security settings, and SCIM provisioning capabilities. The application follows a modern Next.js App Router architecture with server and client components, uses Auth0 for identity management, and implements role-based access control with admin/member roles. Key features include organization creation and switching, user invitation workflows, domain verification for SSO, and comprehensive dashboard for managing organization settings, members, and connections.
AutoGPT is a full-stack SaaS platform for building, deploying, and running AI agents. It provides a visual agent builder (blocks), a copilot chat interface that can generate and orchestrate agents from natural language, a marketplace for sharing agents and skills, team/experts management with scheduling and credential stacks, and a subscription billing system with Stripe. The architecture is a multi-service backend (FastAPI, PostgreSQL, Redis) with a Next.js frontend, supporting real-time WebSocket execution events, OAuth integrations with 45+ providers, and feature flags via LaunchDarkly and PostHog. The platform is dual-licensed (Polyform Shield for platform code, MIT for classic code) and supports both hosted SaaS and self-hosted deployment. The codebase is organized into two major areas: `autogpt_platform/` (the current platform) and `classic/` (legacy AutoGPT and Forge). The platform backend uses a block-based execution system where each integration (Google, Slack, GitHub, etc.) is a self-contained block with typed I/O schemas, cost tracking, and credential management. The frontend features a rich component library with dynamic form rendering (RJSF), responsive dialog/drawer patterns, and extensive state management via TanStack Query and Zustand. Key entry points include the copilot chat UI, the agent library, marketplace, team management, and admin panels. Primary data flows involve user input through the copilot or builder, which triggers graph execution via the execution manager, with events streamed over WebSocket. Credits are deducted per block execution, and billing is handled through Stripe subscriptions with trial management. Analytics events are sent to PostHog and DataFast for product metrics. The system relies on external dependencies including PostgreSQL (with pgvector), Redis, Stripe, LaunchDarkly, PostHog, Sentry, and numerous third-party APIs for integrations.
JSON Crack is an open-source, browser-based tool for visualizing, formatting, converting, and exploring JSON, YAML, CSV, and XML data as interactive graphs. The monorepo (Turborepo) contains four workspaces: a Next.js web app (apps/www) that provides the full editor experience with a Monaco-based text editor, split-view layout, graph canvas, and various utility modals (jq, JSONPath, schema validation, code generation); a VS Code extension (apps/vscode) that embeds the same graph view as a webview panel; a Chrome extension (apps/chrome-extension) that injects a 'Raw'/'Graph' toggle on any JSON page; and a reusable React component package (packages/jsoncrack-react) that exposes `JSONCrack` as a standalone component along with a `parseGraph` utility and TypeScript types. All data processing happens client-side — the app is a fully static Next.js export served behind NGINX. The architecture is frontend-only, relying on Zustand for state, reaflow for graph layout, react-zoomable-ui for pannable/zoomable canvas, and jsonc-parser for AST-driven parsing. The codebase is well-organized, with clear separation of concerns, good TypeScript coverage, and unit tests in the core package.
Postiz is a full-stack, open-source social media scheduling and publishing platform that supports 30+ platforms (Instagram, TikTok, LinkedIn, YouTube, X, Facebook, etc.). The system is built as a pnpm monorepo with four main applications: a Next.js frontend (App Router), a NestJS backend REST API, a Temporal-based workflow orchestrator for reliable post publishing and token refresh, and a Chrome extension for cookie-based authentication. It also includes a CLI app, a public SDK (@postiz/node), and a shared libraries layer for business logic, database access (Prisma + PostgreSQL), and integrations. Key architectural patterns include an abstract social provider base class (SocialAbstract) that all platform integrations extend, a Temporal v1.8+ workflow engine with versioned posting workflows (v1.0.1 through v1.0.8), an upload factory abstracting local and Cloudflare storage, an MCP server for AI agent tools (scheduling, content generation via LangGraph), a plug/auto-reply system, and a short-link abstraction with multiple providers. The frontend uses Zustand for state management, SWR for data fetching, CopilotKit for AI textarea integration, and Mantine/Tailwind for UI. The system handles OAuth flows, subscription billing via Stripe, team collaboration, webhooks, and admin monitoring. The codebase demonstrates strong engineering with reusable abstractions for social integrations, storage, email, and short-linking, though it carries some technical debt from organic growth (multiple workflow versions, hardcoded strings, and suppressed TypeScript strictness).
This repository implements an AI-powered diagram generation and editing application that integrates draw.io with large language models. Users describe diagrams in natural language, and the system generates, edits, and validates draw.io XML diagrams through a chat interface. The architecture is a Next.js 16 web application with App Router, supporting multiple AI providers (OpenAI, Anthropic, Google, AWS Bedrock, DeepSeek, Ollama, etc.) via the Vercel AI SDK. It includes a desktop Electron app with offline draw.io support, an MCP server for external AI agent integration (Claude, Cursor, VS Code), and an admin panel for runtime configuration of models, access controls, and observability (Langfuse). The application is self-hostable via Docker and deployable to Vercel or Cloudflare Workers. The core workflow involves a chat interface where users send prompts, optionally upload files (images, PDF, text) or URLs, and the AI responds with tool calls to display, edit, or append diagrams. The system handles streaming XML generation, debounced diagram updates, and automatic XML validation/fixing to correct common LLM output issues. It supports multi-page diagrams, shape libraries (AWS, Azure, GCP, etc.), and experimental VLM-based diagram validation. Session history, templates, and diagram versions are persisted in IndexedDB, with optional server-side quota management via DynamoDB. The codebase demonstrates strong engineering practices with comprehensive unit and E2E tests, CI/CD pipelines, multi-platform builds (web, desktop, MCP server), and i18n support for English, Chinese, and Japanese. It features reusable patterns such as a registry-driven admin settings system, DNS-based SSRF protection, and a standalone XML validation library. While the project is actively maintained and uses modern frameworks, its large dependency surface and complex configuration precedence (env vars, admin panel, file-based) introduce some maintenance overhead.
This repository is a distribution and development monorepo for "Agent Skills" — packaged instruction sets, rule files, and CLI tooling that extend AI coding agents to work more effectively with Vercel, React, Next.js, and React Native. The dominant artifact is the `vercel-optimize` skill, a sophisticated performance/cost audit pipeline. It starts by collecting real signals from the Vercel CLI (metrics, usage, project config, route data), then applies deterministic pure-JS gates and AST-based code scanners to generate candidate investigation targets. LLM sub-agents receive structured investigation briefs with playbooks, citations, and support-topic guardrails; their outputs are collected, mechanically verified, sanitized, deduplicated, graded, and rendered into a customer-safe markdown report. This is not a web service or library in the traditional sense — it is a toolchain of executable scripts plus knowledge artifacts designed to be installed into agent environments via `npx skills add`. The repository also contains curated knowledge bases (`react-best-practices`, `react-native-skills`, `composition-patterns`, `react-view-transitions`, `web-design-guidelines`) stored as markdown rules with YAML frontmatter. A build package (`react-best-practices-build`) parses these rules, validates them, and compiles them into `AGENTS.md` files for consumption by agents. The engineering quality is strongest in `vercel-optimize`: it has extensive `node:test` coverage, real CLI output fixtures, a modular gate/scanner/sanitizer architecture, claim-based verification, and careful handling of Vercel API rate limits. The main risks are external dependency drift — Vercel CLI output schemas, metric IDs, Observability Plus availability, and Next.js/React framework versions all change over time — and the inherent fragility of parsing LLM sub-agent output. Although the repo contains large amounts of markdown knowledge content, the dominant character is application/tooling: it ships executable entry points, has unit tests, CI workflows, and a build pipeline. It is not a data-research repository, and the metric fixtures exist to test the tooling rather than to answer analytical questions.
This is a monorepo for Auth.js (formerly NextAuth.js), a framework-agnostic authentication library for web applications. The core engine (`@auth/core`) handles OAuth/OIDC, email/passwordless, credentials, and WebAuthn/Passkey authentication flows. It provides a unified API for session management (JWT or database-backed), CSRF protection, and cookie handling. The library is designed to be integrated into multiple frameworks via separate packages: `@auth/nextjs`, `@auth/sveltekit`, `@auth/express`, `@auth/qwik`, and `@auth/solid-start`. Each framework package adapts the core `Auth` function to the framework's request/response model, offering server-side handlers, middleware, and client-side hooks. The repository also includes over 80 built-in OAuth/OIDC provider definitions (e.g., Google, GitHub, Discord, Auth0) and 20+ database adapters (e.g., Prisma, Drizzle, MongoDB, PostgreSQL, DynamoDB) that implement a standard `Adapter` interface for user persistence. The project is now part of Better Auth, and the README recommends new projects use Better Auth unless specific feature gaps exist. The monorepo contains development apps, example applications, and a comprehensive documentation site built with Nextra.
This repository is a CLI tool (`api-platform`) that scaffolds new API Platform projects. It generates Symfony or Laravel project skeletons with optional Docker infrastructure, Next.js PWA, React-admin SPA, and AI agent instruction files. The tool configures API formats (JSON-LD, JSON:API, HAL) and documentation viewers (Swagger UI, ReDoc, Scalar). It fetches Docker files from a pinned commit of `dunglas/symfony-docker` and patches compose.yaml for CORS headers. The codebase is well-structured with clean abstractions, idempotent patching patterns, and comprehensive test coverage. It demonstrates professional PHP engineering using Symfony Console components and modern PHP features.
Dillinger is a cloud-enabled, online Markdown editor with live preview, export to Markdown, HTML, and PDF, and synchronization with cloud storage services including GitHub, Dropbox, Google Drive, OneDrive, and Bitbucket. Built with Next.js 14 (App Router), the application uses Monaco Editor for editing, Zustand for client-side state management with localStorage persistence, and markdown-it with a rich plugin chain for rendering. It features a modular architecture with API routes for OAuth flows and file operations per cloud provider, a versioned public REST API (v1) for rendering and export, and separate packages for a CLI tool and an MCP server for LLM integration. The codebase is well-organized with clear component separation (editor, preview, sidebar, modals, UI primitives), custom hooks per integration, and comprehensive unit and E2E test coverage. Auxiliary agent/skill files and design system CSVs exist in the repository but are development tools, not part of the application runtime.
Pi Web is a full-stack Next.js application that provides a browser-based interface for the Pi coding agent, an AI-powered coding assistant. It shares session files, configuration, and credential storage with the Pi CLI, enabling users to manage AI coding sessions, browse and edit files, run terminal commands, and configure models/plugins/skills—all from a web browser. The application is designed for local use, running on Node.js ≥22.19 and opening at 127.0.0.1:30141 by default. Architecturally, Pi Web is a Next.js 16 App Router application with React 19 client components, a comprehensive REST API layer, and real-time streaming via Server-Sent Events (SSE) for agent events and terminal output. It features a PWA with service worker support for push notifications and offline fallback, optional password authentication with HMAC-signed session tokens, and an extension system for custom UI widgets. The frontend is organized around a chat-centric workspace with resizable panels for session management, file viewing, terminal emulation, and configuration. Key capabilities include session lifecycle management (create, fork, rename, delete, branch), file browsing with syntax highlighting and previews (images, audio, video, PDF, DOCX), Git worktree support, subagent runtime for background tasks, model catalog configuration with provider presets, and internationalization (English, Simplified Chinese, Traditional Chinese). The codebase is extensively tested with over 100 test files using Node's test runner and jiti for TypeScript imports, covering both unit and integration tests for API routes, components, and utilities.
Intent UI is a copy-paste accessible React component library built on React Aria Components and styled with Tailwind CSS v4. It follows the shadcn/ui distribution model: components are installed via CLI (`npx shadcn@latest add @intentui/<component>`) from a registry served by the included Next.js documentation site. The repository contains over 80 UI components (buttons, forms, overlays, charts, navigation, layouts, etc.), each with multiple usage examples and comprehensive MDX documentation. The architecture is a Next.js App Router application that also functions as the component registry host, with custom build scripts generating registry JSON, icon metadata, and LLM-friendly documentation exports. External dependencies include React Aria Components for accessibility, Recharts for charts, motion for animations, sonner for toasts, and tailwind-variants for styling variants. The library is monetized through sponsor tiers and premium design assets, but the core components are MIT-licensed.