Mage is an open-source data pipeline orchestration platform that combines a visual notebook-style editor with a production-grade scheduling and execution engine. The system enables users to build, run, and monitor data pipelines composed of Python, SQL, R, and dbt blocks. Architecturally, it is a full-stack web application with a Python backend (Tornado-based server, SQLAlchemy ORM, REST API) and a Next.js/React frontend with a custom component library. Key entry points include the CLI (`mage` command), the web UI served by `mage_ai/server/server.py`, and the API layer at `mage_ai/api/` which exposes CRUD resources for pipelines, blocks, runs, schedules, users, and integrations. Data flows center around pipeline execution: blocks are connected in a DAG, each block can be a data loader, transformer, or exporter. Execution is handled by a configurable executor (local, K8s, EMR, PySpark) and scheduled via a built-in scheduler or external triggers. The platform integrates with dozens of data sources and destinations through a Singer-based integration framework, supports streaming pipelines, and includes advanced features like RBAC, version control, AI-assisted pipeline generation, and a command center for global search. It depends heavily on external services such as cloud storage (S3, GCS, Azure), databases (PostgreSQL, BigQuery, Snowflake, etc.), and authentication providers (OAuth, LDAP, OIDC).
Tape is a decentralized video-sharing platform built on Lens Protocol. The monorepo contains multiple frontends: a legacy Next.js app (apps/web), a newer Vite + TanStack Router rewrite (apps/web-vite), an Expo/React Native mobile app, an embeddable video player, and an Open Graph image generator. The backend consists of a Hono API (apps/api) for oEmbed, DID resolution, metadata, and event ingestion, plus a cron service (apps/cron) for cleanup, analytics flushing, and S3 backups. Smart contracts for permissionless signup live in apps/contracts. The platform supports video upload, short-form bytes, comments, mirrors, collects, tips, follows, notifications, search, and profile management, all interacting with Lens Protocol's GraphQL APIs and on-chain contracts. Data flows through several layers: media is uploaded to IPFS/S3/Arweave, metadata is stored on Arweave or IPFS, and social actions are executed via Lens Protocol typed-data signing and broadcasting. The platform also runs an in-house analytics pipeline: browser events are queued through a service worker to Redis, flushed to ClickHouse by cron jobs, and backed up to S3. Postgres (via Prisma) stores platform-level data such as allowed tokens, profile toggles, curated profiles, and platform stats. Redis is used for caching and queueing throughout. Although primarily an application, the repository has a meaningful data/analytics component (ClickHouse schema, event/trail tracking, Redis-backed queues, S3 backup jobs) that could be reused independently. The codebase is actively maintained but carries migration debt: two web frontends, two UI kits (packages/ui and packages/winder), two Lens GraphQL clients (v1 and v2), and commented-out cron services indicate an in-progress transition. No meaningful test suite is present; CI focuses on Biome checks and builds.
FarmBot Web App is the cloud-based control panel for FarmBot, an open-source CNC farming robot. It provides a full-stack web application (Rails API + React/TypeScript SPA) for managing devices, creating automated sequences via a visual CeleryScript AST editor, scheduling farm events, monitoring telemetry and logs, managing plants/weeds/tools, and viewing real-time 2D/3D garden maps. The backend is a monolithic Rails app with PostgreSQL, RabbitMQ/MQTT for device communication, and DelayedJob for background processing. The frontend is a complex Redux SPA with extensive 3D visualization using Three.js. The system supports multiple hardware variants and includes firmware update management, camera calibration, and AI-assisted feedback. The codebase is actively developed with a large test suite, but exhibits some technical debt like legacy AST storage paths, future-dated migrations, and heavy mocking in tests.
This repository is a community-driven collection of Streamlit 'extras' — custom components and utilities that extend Streamlit's functionality. It is a Python library (package `streamlit-extras`) that provides over 40 self-contained subpackages, each implementing a specific UI widget, layout helper, or data exploration tool. The architecture is modular: each extra is a subpackage under `src/streamlit_extras/` with a standardized metadata convention (`__title__`, `__desc__`, etc.) and a central `@extra` decorator for registration. Some extras are pure Python wrappers around Streamlit's native APIs (e.g., `grid`, `stateful_button`, `stoggle`), while others are full Custom Components v2 (CCv2) with React/TypeScript frontends built with Vite (e.g., `three_viewer`, `json_editor`, `sigma_graph`). The build system uses Hatch with a custom build hook to compile React frontends during wheel packaging. The gallery app (`gallery/streamlit_app.py`) serves as a demo and documentation explorer. The codebase is well-organized but has several deprecated extras that rely on private Streamlit APIs, and test coverage is limited to metadata validation. Overall, it is a solid, actively maintained library with reusable patterns for Streamlit component development.
Xibo CMS is a full-stack digital signage content management system that enables users to create, schedule, and manage content displayed on screens. The backend is built with PHP (Slim framework, Symfony EventDispatcher, Phinx migrations) and exposes RESTful APIs consumed by a modern React/TypeScript SPA frontend (Vite, TanStack Query, Tailwind CSS). It supports player communication via XMR (message relay) and legacy SOAP-based XMDS. Key features include layout and playlist management, media library, scheduling with dayparting and recurrence, reporting (proof of play, bandwidth, session history), OAuth2 authentication, multi-tenancy via folders and permissions, and a widget/module system with connectors. The codebase is large and actively maintained, with extensive frontend tests (Vitest) and Docker-based development/deployment. However, it carries some technical debt from a legacy jQuery/Bootstrap UI that coexists with the modern React frontend, and a high volume of database migrations indicates long evolution.
The repository is a full-stack application template providing role-based access control (RBAC) with a modern frontend and multiple backend options. It features a React/Vite frontend built with Shadcn UI and Tailwind CSS, offering comprehensive UI components, dashboards, and charting capabilities. Two backend implementations are provided: Spring Boot (Java) and NestJS (TypeScript), both featuring JWT authentication, PostgreSQL integration, and CRUD operations for users, roles, permissions, and groups. The frontend showcases a well-crafted component library including reusable UI primitives, custom extensions like tree selectors and context menus, and themed chart containers. State management is handled via Zustand, with internationalization via react-intl and API mocking using MSW. The backends follow standard layered architectures with service-repository patterns, DTO validation, and security configurations. While the Spring Boot backend contains a non-standard Java 25 version specification (likely a typo) posing build risks, the NestJS backend uses current LTS Node.js versions. The project demonstrates solid full-stack engineering with modular design, clear separation of concerns, and reusable UI patterns. Despite the Java version concern in one backend, the template remains a valuable foundation for enterprise admin panels with modern tooling.
This repository contains the official AntV website, built with Astro and React islands. It serves as the primary marketing and documentation portal for AntV's data visualization libraries (G2, G6, L7, etc.), featuring a hero section, interactive chart demos, a theme customizer that generates downloadable JSON palettes, and a wealth of bilingual (Chinese/English) specification documents covering design principles, chart types, components, and interaction patterns. The site is a static Jekyll-like documentation site, but with substantial client-side interactivity delivered through React components that embed G2Plot and G6 charts. The architecture is a typical modern static site: Astro handles content collections and build, React components are mounted as islands for interactive sections, and JSON files drive most of the home page content. The docs are written in Markdown with frontmatter and use a custom Astro loader to integrate with the @antv/astro-theme-antv theme package. The code is clean and well-organized, with a clear separation between data, libs, and components. The most reusable component is an overflow text truncation utility that gracefully degrades to a tooltip on overflow, demonstrating good engineering practices. While the repository is primarily a content and marketing site, it contains a few genuinely reusable patterns, though most are tightly coupled to the AntV ecosystem. The lack of a lockfile and the use of an older G6 version indicate some technical drift, but the project appears actively maintained with recent commits and CI/CD deployment.
This repository is the full-stack personal website of Max Stoiber (mxstbr.com), built with Next.js 16, TailwindCSS, and TypeScript. It serves a dual role: a public-facing blog and digital garden, and a private family productivity suite called 'MaxOS' that simulates a Windows 98 desktop environment. The public side includes MDX blog posts, Hashnode-synced notes, an RSS feed, and an investing page. The private side is a full-featured operating system shell with iframe-based apps: a calendar (with events stored in Redis), a finance portfolio tracker (pulling from Tiingo), a reminder system, a todo list, and a sophisticated chore management system (Chores2) for tracking kids' chores, rewards, and completions. The Chores2 subsystem is the most architecturally rich part of the codebase. It uses a layered domain-driven design with types, domain logic, commands, a service layer, a repository (with both in-memory and Redis implementations using compare-and-set transactions), MCP tool definitions for AI integration, and a notification outbox pattern for reliable Telegram delivery. The system supports time-window-based chore scheduling, period bonuses, approval workflows, and undo. It was recently rebuilt from a legacy version, with all features documented and verified in design docs. The codebase also integrates AI heavily: a Clippy chat assistant (powered by OpenAI) accessible via web and Telegram, and an MCP server that exposes tools for calendar, chores, and finance, enabling ChatGPT and other AI agents to read and mutate family data. The architecture is modern, with server actions, streaming, and Redis-backed state. However, the repo shows signs of being a single-developer project with some duplication (two active chore board UIs) and hardcoded secrets (parental PIN).
EmailThing is a self-hosted email service providing web (PWA), CLI, and API interfaces for sending and receiving emails with custom domains. The system consists of a Bun-based backend API using PostgreSQL with Drizzle ORM, a React/Next.js PWA with Dexie IndexedDB for offline capabilities, and a CLI tool for management. It handles email storage via S3, authentication with JWT/sessions and passkeys, rate limiting with Redis, and integrates with external email services for sending while using Cloudflare Workers for reception. The architecture follows a monorepo pattern with clear separation: apps/api (backend server), apps/pwa (frontend interface), apps/cli (terminal tool), and shared packages for database, constants, and SDK. Key features include multi-user mailbox management, aliases, custom domain support, team collaboration, end-to-end encryption for sensitive data, and real-time synchronization between client and server. The system emphasizes user control over email infrastructure while providing modern web application experiences.
Pogly Standalone is a real-time collaborative overlay editor designed for streamers. It allows multiple users to jointly create and manage stream overlays (text, images, widgets) that can be displayed in streaming software like OBS. The application features a React frontend with TypeScript, utilizing Material-UI and styled-components for the UI, and a C# backend powered by SpacetimeDB for real-time state synchronization. Key functionalities include drag-and-drop interface, layout management, role-based permissions (owner/moderator/guest), integration with streaming platforms (Twitch, YouTube, Kick) and emote services (7TV, BetterTTV, Tenor), and persistent storage via Docker volumes. The architecture follows a modular structure with clear separation of concerns: the frontend handles user interactions and rendering, while the SpacetimeDB backend serves as the authoritative state store, pushing updates to all connected clients via WebSocket. Deployment is containerized using Docker with Caddy serving the frontend and proxying to SpacetimeDB.
This repository is a comprehensive React workshop containing three main applications: a vacation search SPA, an e-commerce store using React Router's data APIs (loaders/actions), and a Next.js app demonstrating React Server Components. It also includes extensive course materials covering React fundamentals, advanced hooks, form abstractions, and performance optimization. The applications showcase modern React patterns including context API, custom hooks, component composition, and data fetching evolution from useEffect to React Query to loader functions.
This is a standalone web UI for Midjourney image generation, built as a Next.js 14 application. It provides a prompt editor, image preview with upscale/variant/reroll actions, a task history list, and settings to configure a midjourney-proxy service. The app can run standalone or be embedded as a LobeChat plugin via an iframe. It uses React with Zustand for state management, SWR for data fetching, Immer for immutable state updates, and antd-style for theming. The backend consists of two API routes: one proxies requests to the midjourney-proxy service, and another uploads images to Imgur. The codebase is well-structured with clean separation of concerns, i18n support, and responsive design. While the application is functionally straightforward, it demonstrates solid engineering practices including pure reducer functions with unit tests, typed state management, and a modular layout system.
Wavefront is an enterprise AI middleware platform, open-source alternative to tools like UnifyApps and n8n. It provides a full-stack system for building, managing, and deploying AI agents, chatbots, voice agents, knowledge bases (RAG), and AI-powered workflows. The monorepo includes a Python FastAPI backend with a modular, domain-driven architecture (agents, tools, knowledge base, voice, triggers, auth, API proxy), a React/TypeScript management console, background workers (Celery, stream processors), and the `flo_ai` Python agent framework (LLM wrappers, Arium graph engine, tool system). The platform supports multi-tenancy, RBAC, cloud storage abstractions (GCP/AWS/Azure), and pluggable datasource and authenticator modules. While primarily an application, it incorporates RAG pipelines, image embedding services, and model inference, giving it a hybrid character with strong data engineering elements.
DesignFlow Kit is an open-source, full-stack web application that provides an AI-powered UX/Product Design toolkit. It features 8 AI chat assistants for various design workflows (research, personas, journey maps, wireframes, testing, workshops, information architecture, and general analysis), a Kanban-style sprint board with drag-and-drop and voice recording, a dashboard for progress tracking, a catalog of 41+ integrations, and pre/post-design kits. The frontend is built with React 18, TypeScript, Tailwind CSS, and shadcn/ui components, using Wouter for routing and TanStack Query for data fetching. The backend is an Express.js server with Drizzle ORM and PostgreSQL (with in-memory fallback), integrating with OpenAI GPT-4o for streaming chat, Whisper for transcription, and Resend for email-based OTP authentication. The application is deployed as a monolith via Replit-specific integrations, though the core stack is portable. The codebase is well-structured with clear separation of concerns, but suffers from significant duplication across the 8 chat page components and relies heavily on static data files for tool/integration catalogs. No automated tests are present, and the OTP flow includes a visible demo code in development mode, signaling some immaturity. Overall, it is a functional and feature-rich tool with moderate reusability of its core components.
AgenticSeek is a private, local autonomous AI assistant built as an alternative to Manus AI. The system features a multi-agent architecture with six specialized agents (Casual, Coder, File, Browser, Planner, MCP) selected by a hybrid router using BART zero-shot classification and an adaptive few-shot classifier. It provides a React frontend, FastAPI backend with Celery, CLI with voice support, and Docker Compose orchestration for self-hosted services including SearxNG search and Redis caching. The codebase demonstrates solid engineering with clean abstractions for LLM providers (14+ options), tool execution, browser automation, and workspace isolation. It is under active development but shows signs of technical drift in deprecated components (llm_server, SerpApi-based web search) and fragile browser automation. The architecture is modular and contains several reusable patterns, though the codebase is tightly coupled to its specific agent system and has substantial external dependencies.
Pomatez is a cross-platform Pomodoro timer desktop application built with a monorepo architecture managed by Lerna and Yarn workspaces. It provides a customizable timer with focus/break sessions, task management, system tray integration, desktop notifications, full-screen break enforcement, Discord Rich Presence, and auto-update capabilities. The application is implemented with two backend options: a primary Electron backend and an experimental Tauri (Rust) backend, both sharing a common React frontend (renderer) and a shared constants package. The frontend uses Redux Toolkit for state management, styled-components for theming (light/dark), react-i18next for internationalization (English, Spanish, Chinese, Japanese), and react-beautiful-dnd for task list drag-and-drop. The repository also includes a Gatsby-based marketing website for downloads and feature showcases. The core timer logic is driven by a React context (CounterContext) that manages countdown, session transitions, and full-screen break states. User settings and tasks are persisted to localStorage (and electron-store for the Electron backend) with debounced Redux store persistence. The application exposes a connector abstraction (ConnnectorContext) that decouples the frontend from the backend platform, allowing the same UI code to work with both Electron and Tauri via platform-specific connectors. The Electron main process handles window management, system tray, global shortcuts, and auto-updates, while the Tauri backend provides similar functionality through Rust commands. External dependencies include node-notifier for notifications, discord-rpc for Rich Presence, and electron-updater/tauri-plugin-updater for auto-updates. The codebase demonstrates solid engineering practices with reusable UI components, custom hooks, and a well-organized store structure. However, it shows signs of technical drift with outdated dependencies (React 16, TypeScript 4.9.4, deprecated husky v4) and the dual-backend approach introduces code duplication and maintenance overhead. Test coverage is minimal, with only one unit test file found. The Tauri backend is marked as experimental and has some incomplete features (e.g., set_ui_theme is a no-op). Overall, Pomatez is a functional and feature-rich desktop application with a clean frontend architecture, but its backend complexity and dependency age suggest moderate refactoring needs.
Kanaries/Rath is an open-source augmented analytics BI platform that automates exploratory data analysis, causal discovery, and dashboard creation. It is a full-stack application with a React/TypeScript frontend (Vite, MobX, shadcn/ui) and multiple Python microservices (causal inference, narrative insight generation, database connectors). The system ingests data from files, databases (PostgreSQL, ClickHouse, MySQL, etc.), and REST APIs, then provides automated visualization (mega-automation), semi-automated exploration, causal analysis (PC, FCI, GES, XLearner), and interactive dashboard building. It also includes custom Vega renderers (WebGL, Painter) for high-performance chart rendering and an Electron desktop wrapper. While primarily an application, it contains significant data research components such as causal discovery algorithms, statistical insight detection, and text pattern extraction, making it a hybrid tool for both data exploration and advanced analytics.
This repository provides `react-photo-view`, a React component library for image and custom element preview with touch gestures, animations, and keyboard navigation. The library exposes three primary components: `PhotoProvider`, `PhotoView`, and `PhotoSlider`. `PhotoProvider` manages a group of images via React context, tracks visibility and index, and renders a `PhotoSlider` portal. `PhotoView` registers individual images or custom render nodes with the provider and handles thumbnail click/double-click triggers. `PhotoSlider` renders a full-screen overlay with a backdrop, swipeable carousel, zoom/pan/drag support, and optional toolbar/overlay customizations. The architecture is monolith-like within the library but decoupled through context and custom hooks. Key entry points are the `PhotoProvider` wrapper and `PhotoView` child components. External dependencies include React 16.8+ and ReactDOM. The codebase demonstrates strong craftsmanship: physics-based scrolling, debounced/tap gesture handling, and modular utility functions. No unit tests are present, and TypeScript version (4.9) and some dependency versions are slightly behind current, but the library is actively maintained and functional.
A well-structured monorepo for building cross-platform Expo (React Native) applications using pnpm and Turborepo. The repository demonstrates a scalable architecture with three shared packages (eslint configuration, reusable UI components, and a home feature) and a single example Expo app that leverages Expo Router for navigation, react-native-reanimated for animations (parallax scroll, wave animation), expo-haptics for haptic feedback, and expo-symbols/expo-image for platform-adaptive icons and images. The code is organized following modern React Native best practices: typed routes, strict TypeScript, automatic dark/light mode, absolute imports, and Jest + testing-library/react-native tests for components. CI/CD is fully implemented via GitHub Actions with workflows for linting, building, testing, EAS deployments, and preview builds. While the application itself is a simple template (home screen with steps, an explore screen with informational collapsibles, and a modal), the architecture showcases a effective monorepo workflow with Turborepo caching and pnpm workspace protocols. The most notable technical components are a cross-platform icon abstraction (SF Symbols to Material Icons), a standalone parallax scroll view with Reanimated, and an in-app browser link adapter—all of which are modular and easily extracted for other projects.
Hyper-RAG is a hypergraph-driven Retrieval-Augmented Generation (RAG) system designed to reduce LLM hallucinations by modeling beyond-pairwise correlations in domain knowledge. The repository provides both a Python library (`hyperrag`) and a full-stack web application with a FastAPI backend and React frontend. The core innovation is the use of hypergraphs to represent complex relationships among entities, outperforming traditional graph-based RAG methods like Graph RAG and Light RAG. The system supports multiple query modes: hyper (full hypergraph), hyper-lite, graph, naive, and direct LLM, with streaming responses. Architecture: The Python library (`hyperrag/`) implements the RAG pipeline: text chunking, entity extraction via LLM, hypergraph construction, vector embedding storage (NanoVectorDB), and query execution. The web UI (`web-ui/`) consists of a FastAPI backend (`main.py`) exposing REST endpoints for file upload, database CRUD, and HyperRAG queries, plus a React frontend with Ant Design and Graphin for interactive chat, hypergraph visualization, and settings management. Docker Compose orchestrates the frontend, backend, and Nginx reverse proxy. Key entry points: `hyperrag/hyperrag.py` (HyperRAG class), `service_api.py` (standalone API), `web-ui/backend/main.py` (FastAPI app). External dependencies include OpenAI/Azure/Bedrock LLM APIs, NanoVectorDB, tenacity, aiofiles, and various Python packages. The system is configurable via `config_temp.py` and `settings.json`. Data flows: Raw text (uploaded or provided) is chunked, entities and relationships are extracted via LLM, hyperedges are constructed, and embeddings are stored. Queries are processed by selecting relevant hyperedges and entities, constructing a context, and generating a response. The system caches LLM responses and supports real-time logging via WebSocket during embedding.