BookWith is a next-generation e-reader application that enhances traditional book reading with AI capabilities. The system allows users to upload and read EPUB books, annotate text, interact with an AI chatbot for contextual questions about the content, and generate AI-powered podcasts from book material. The architecture follows a client-server model with a Next.js/React frontend and a FastAPI/Python backend, employing domain-driven design principles. Key features include a multi-layer memory system for maintaining conversation context, semantic search via Weaviate vector database, and integration with external AI services like Gemini and Google Cloud Text-to-Speech. The frontend uses modern React patterns with Zustand/Jotai for state management, Tailwind CSS for styling, and shadcn/ui-inspired components. The backend utilizes PostgreSQL for relational data, implements clean architecture with separate domain/application/infrastructure layers, and provides a well-structured API with automatic OpenAPI schema generation.
react-py is a React library that enables running Python code directly in the browser by leveraging Pyodide, a Python distribution compiled to WebAssembly. The library provides a PythonProvider context and two hooks (usePython and usePythonConsole) for executing Python scripts and interacting with an interactive console. Python execution occurs in a dedicated web worker via comlink-based RPC, preventing UI blocking. A service worker intercepts synchronous fetch requests from the worker to implement stdin input (e.g., input() function). The library supports loading Pyodide official packages and micropip-installable packages, file system operations (read/write/mkdir/rmdir), module watching for hot-reloading, execution timeouts, lazy worker initialization, and automatic package import detection. The architecture is cleanly separated into provider, hooks, worker scripts, and types, with the documentation site (Docusaurus) serving as both documentation and interactive playground.
GreedyBear is a threat intelligence platform that consumes honeypot logs from T-Pot clusters (Cowrie, Heralding, Tanner, etc.), extracts Indicators of Compromise (IOCs), enriches them with external threat feeds (ThreatFox, AbuseIPDB, FireHol, Spamhaus, MalwareBazaar), and applies machine learning scoring (Random Forest) to predict recurrence probability and expected interactions. The system exposes public and authenticated APIs in multiple formats (JSON, NDJSON, CSV, TXT, STIX 2.1) for threat researchers and supports event ingestion from external sensors. The backend is built with Django/DRF, PostgreSQL, and Elasticsearch, orchestrated via Django-Q cronjobs for scheduled extraction, enrichment, and cleanup. A React SPA frontend provides a customizable dashboard with attack maps, trending attackers, and feed browsing. The architecture uses repository, strategy, and factory patterns, with a clean separation between extraction pipelines, scoring, and API layers. While primarily an application, it has strong data engineering components—ETL pipelines, ML scoring, clustering (MinHash LSH for command sequences), and data enrichment—making it a hybrid that leans application.
Electron Router DOM is a library that facilitates the integration of react-router-dom with Electron applications, enabling window-based routing where each Electron window can have its own routing configuration. The library handles the complexities of loading URLs in development versus files in production, provides type-safe APIs for passing data between main and renderer processes via query parameters, and abstracts away the low-level Electron window management details. It follows a clean architecture with clear separation between main process utilities (registerRoute function) and renderer process components (Router component), supported by shared TypeScript types and utility functions. The library is designed to improve developer experience by eliminating manual management of Electron's loadURL and loadFile methods while maintaining compatibility with react-router-dom's routing patterns.
Outline is a collaborative knowledge base platform built with React and Node.js. It provides real-time document editing via ProseMirror/Yjs, team workspaces with granular permissions, and extensibility through a plugin system. The application features rich text editing, document organization into collections, search functionality, notifications, and integrations with services like Slack, GitHub, and Notion. Architecture follows a monorepo structure with frontend (React/MobX/Styled Components), backend (Node.js/Koa/Sequelize), and shared utilities. Key entry points include the React root (app/index.tsx), Koa server (server/index.ts), and API routes (server/routes/api/). The system relies on PostgreSQL for primary data storage, Redis for caching and job queues, and S3/local storage for file attachments.
Image-Blaster is a generative 3D asset pipeline and web viewer that transforms a single input image into a fully interactive 3D scene. The system uses Claude AI agents to orchestrate a multi-step workflow: image analysis and object extraction, background removal (plate generation), world generation via World Labs (gaussian splats, colliders, panoramas), 3D object generation via FAL (Hunyuan3D or Meshy), and sound effect generation via ElevenLabs. All generated assets are stored locally with a deterministic indexed naming convention and request metadata for resumability. The frontend is a React 19 + Three.js (R3F) application with physics (Rapier), post-processing (Bloom, DoF, motion blur), splat rendering (SparkJS), and a full scene editor with undo/redo, transform controls, and asset library. The architecture is a monorepo with a Vite dev server that serves assets and provides a CRUD API for scene projects. While the system is primarily an application, it also contains a data pipeline aspect in its asset generation scripts, which follow a consistent lifecycle of submission, polling, download, and metadata writing. The codebase demonstrates strong engineering practices with reusable patterns like the FAL queue wrapper, indexed file resolution, camera gesture hooks, and error boundaries. However, it is heavily dependent on external cloud APIs (FAL, World Labs, ElevenLabs) and Claude agent tooling, with no offline fallback or mock mode.
Runtipi is a self-hosted homeserver orchestrator: a web-based control plane for installing, updating, backing up, and managing Docker Compose applications on a single server. In production it runs as a NestJS backend, a React frontend, and a shared TypeScript schema package, with PostgreSQL as the primary datastore, RabbitMQ for asynchronous job queues, Dockerode for container control, and Traefik as the reverse proxy and TLS/forward-auth gateway. The app-store model clones external git repositories containing app manifests and compose definitions, then validates and renders them through a dynamic form system. The architecture is a monolithic backend organized around modules for app lifecycle, marketplace, app stores, backups, auth, links, settings, and i18n; long-running operations are executed through a command/handler pattern with per-app async mutexes and schema-validated RabbitMQ event queues.
ReactPage (formerly ORY Editor) is a production-grade WYSIWYG page editor built in React. It provides a visual drag-and-drop interface for composing page layouts from a plugin system of content and layout cells. The editor stores its state as a structured JSON tree (not HTML), enabling versioning, migrations, and server-side rendering. It supports multi-language content, undo/redo, inline editing via Slate, and a read-only mode for lightweight rendering. The architecture is a monorepo with a core editor package, a rich set of content plugins (Slate rich text, image, video, spacer, divider, HTML5 video), a layout plugin (background with gradients/images), and a ReactAdmin integration. The editor is highly extensible: custom cell plugins can define their own renderers, controls (auto-generated forms via uniforms), cell styles, and data migrations. The Slate plugin itself is extensible via factory functions for marks, blocks, and data plugins. The project is used in production by several companies for CMS-like page building.
CoAI (formerly ChatNio) is a full-stack AI chat platform and LLM gateway that provides a unified chat interface and OpenAI-compatible API proxy for 16+ AI model providers (OpenAI, Anthropic Claude, Google Gemini, Midjourney, DeepSeek, etc.). The system is built with a Go backend (Gin framework) and a React/TypeScript frontend (Redux, Tailwind CSS, Radix UI), with MySQL and Redis for persistence and caching. It supports real-time WebSocket chat, streaming responses, conversation management, file upload, web search, image generation, and a plugin system (MCP). The platform includes a comprehensive billing and subscription system with elastic per-token pricing and tiered plans (Basic/Standard/Pro), along with an admin dashboard for user management, channel configuration, analytics (model usage, request volume, revenue, errors), and system settings. It also features invitation codes, redeem codes, affiliate marketing, and multiple payment gateway integrations (Stripe, WeChat Pay, etc.). Architecturally, the backend employs an adapter pattern for AI providers, a channel manager for load balancing and retries, and a WebSocket connection manager with rate limiting. The frontend is heavily componentized with shadcn/ui and includes i18n support (English, Chinese, Japanese, Russian). Deployment is supported via Docker Compose, Zeabur, and a Tauri desktop app. While the codebase is well-structured and feature-rich, it shows signs of technical drift such as copy-pasted processor files across adapters, hardcoded model constants, and a large dependency surface. The open-source version is Apache 2.0 licensed, with a commercial 'CoAI Pro' tier offering additional features.
This repository is a production-grade, full-stack enterprise AI agent platform developed by iFlytek (Astron Agent). The system allows organizations to create, configure, deploy, and manage conversational AI agents (bots) with advanced workflow automation, knowledge retrieval (multi-strategy RAG), a plugin ecosystem (including MCP and HTTP tools), and multi-tenant team collaboration. The architecture is polyglot and service-oriented: a Java Spring Boot console backend handles bot lifecycle management, publishing to channels (API, WeChat, Feishu, marketplace), RBAC permissions, enterprise spaces, and notification systems. Python FastAPI core services power the workflow engine (20+ node types including LLM, code, decision, memory, knowledge), agent runtime with skill sandbox execution, knowledge indexing and retrieval, and plugin integrations (link server, RPA, MCP). A Go service manages tenant authentication and app key verification. The React + TypeScript frontend provides an interactive console for workflow design, model management, resource management (databases, knowledge bases, skill files), trace logs, and chat interfaces. External dependencies include multiple LLM providers (iFlytek Spark, OpenAI, Anthropic, Google, DeepSeek), MySQL, Redis, Kafka, S3-compatible storage, and Casdoor for SSO. The codebase demonstrates professional engineering with test coverage (JUnit, pytest, Jest), Flyway and Alembic database migrations, CI/CD pipelines, and a modular design using strategy, factory, and AOP patterns. However, it shows signs of complexity from polyglot maintenance, some duplicated frontend components, and legacy credential handling that has been addressed through targeted migration fixes. Overall, it is a well-maintained, actively developed platform suitable for mid-to-large enterprise deployments.
Onsen UI is a comprehensive mobile UI framework for building hybrid mobile apps and progressive web apps (PWAs) with native-like interfaces. The repository is a monorepo containing a core library built on Web Components, CSS components with iOS and Material Design theming, and official bindings for React, Vue 2, Vue 3, Angular 2+, and legacy AngularJS. The core defines custom HTML elements (e.g., `<ons-navigator>`, `<ons-tabbar>`, `<ons-dialog>`) that encapsulate mobile-specific UI patterns such as navigation stacks, tab bars, side menus, pull-to-refresh, lazy lists, and various form controls. The CSS component library provides a consistent, themable styling layer via CSS custom properties and BEM-like modifier classes. Framework bindings wrap these core elements for seamless integration with modern frontend frameworks. The repository also includes example applications, a CSS component previewer, and extensive documentation schemas. While the framework is mature and feature-rich, it shows signs of technical drift with deprecated APIs, multiple legacy binding packages, and a complex build infrastructure. It is actively maintained but appears to be in a stabilization phase rather than rapid development.
Hippy is a cross-platform mobile application framework developed by Tencent that enables developers to build native mobile apps using JavaScript with React or Vue. It provides a JS driver layer that communicates with native renderers on Android, iOS, OpenHarmony, and Web via a bridge system. The architecture is modular: a DOM layer manages the virtual tree and layout (using Taitank or Yoga), native renderers create platform-specific UI components, and a virtual file system (VFS) handles resource loading. The framework includes a full devtools backend implementing Chrome DevTools Protocol for debugging, performance monitoring, and DOM inspection. Key entry points include the JS bootstrap (hippy.js), native engine managers (HippyEngine on Android, HippyBridge on iOS), and the JS framework adapters (hippy-react, hippy-vue, hippy-vue-next). External dependencies include V8, Hermes, JSC, or JSH JavaScript engines, and platform-specific SDKs (AndroidX, UIKit, ArkUI). The codebase is large and actively maintained, with multiple renderer implementations and both Vue 2 and Vue 3 support, though some duplication and deprecated code exist.
This repository is a full-stack web application for AI-driven 3D modeling. Users describe a design in natural language, and an AI agent generates parametric OpenSCAD code or creates a 3D mesh. The system is production-grade: it uses React 19 + TypeScript with TanStack Router and Vite on the frontend, Supabase for authentication, storage, and database, and multiple AI providers (Anthropic, Google, OpenAI, fal.ai) for model generation. It supports parametric CAD (OpenSCAD compiled via WebAssembly in a Web Worker) and creative mesh generation (text/image to 3D via external APIs). The application includes billing via an external service, token-based usage tracking, conversation history with branching, public sharing links, and 3D model export (STL, OBJ, GLB, etc.). While primarily an application, the repository also contains a benchmarks directory (13 documented OpenSCAD models) that demonstrate the AI-to-CAD capability and serve as output artifacts rather than research pipelines.
react-native-webrtc is a React Native native module that provides a JavaScript API for WebRTC, enabling real-time communication in mobile apps. It wraps Google's WebRTC library (via a fork by Jitsi) and exposes standard WebRTC objects like RTCPeerConnection, MediaStream, and RTCDataChannel to React Native. The architecture is a typical React Native native module: TypeScript bindings in src/ communicate with Android Java and iOS Objective-C native code through the bridge. Key entry points include the module's index.ts and the native WebRTCModule classes. The library handles media acquisition (getUserMedia, getDisplayMedia), peer connection management, data channels, screen sharing, and video effects. It includes example apps for iOS, macOS, and tvOS, but no production app. Reusable components include a custom EventEmitter for native event handling, a Permissions wrapper, and video effect processor interfaces. Maintenance is active with recent commits, but the library has some technical drift: it targets an older React Native version (0.71) in dev dependencies, uses synchronous blocking native methods that may be deprecated, and relies on a custom WebRTC fork that requires separate maintenance. No automated tests exist beyond linting.
Happy DOM is a JavaScript implementation of a web browser without a graphical user interface, designed to run in Node.js. It provides a comprehensive simulation of browser APIs including the DOM, HTML/SVG elements, CSSOM, Fetch, WebSocket, Canvas, Custom Elements, Shadow DOM, and more. The library is primarily used as a test environment for JavaScript frameworks (React, Vue, Angular, Lit, etc.) and supports server-side rendering via an optional server-renderer package. The codebase is a monorepo containing the core happy-dom package along with companion packages for global registration, Jest environment, server rendering, and a pluggable canvas adapter. It is actively maintained with thousands of tests and a large community. However, it exhibits moderate technical drift: some APIs are incomplete, there is significant boilerplate duplication across SVG/HTML element implementations, and a few deprecated settings linger. Overall, it is a solid, well-structured library but not exceptional in craftsmanship due to the repetitive patterns and some incomplete implementations.
The XRP Ledger Dev Portal (xrpl.org) is the official documentation website for the XRP Ledger, built with Redocly Realm and a custom React theme. It provides comprehensive developer documentation, interactive tutorials, multi-language code samples (JavaScript, Python, Go, Java), and developer tools such as a WebSocket API explorer, TOML checker, and transaction sender. The site includes a large Brand Design System (BDS) of reusable React components (ButtonGroup, TileLink, CarouselFeatured, PageGrid, etc.) and custom Markdoc tags for content authoring. Background automation includes a Python script for generating release notes from GitHub and a scheduled job to fetch amendment voting data. The portal is actively maintained with frequent blog posts, release notes, and code sample updates, though it contains legacy jQuery scripts and some hardcoded testnet endpoints that represent moderate technical drift.
This is a React-based single-page application that converts Excalidraw drawings into animated SVGs. It provides both an editing mode (using the Excalidraw library) where users can configure animation order and duration per element, and an animate mode where the resulting SVG is rendered with playback controls (play/pause/step/reset). The core animation logic is implemented using SMIL (SVG animations), patching SVG elements with `animate`, `animateMotion`, and `textPath` elements. Users can load drawings from files, libraries, or shareable URLs. The app also exports to SVG and WebM (via screen capture). It is published as an npm package for programmatic use, exposing `animateSvg`, `getBeginTimeList`, and export utilities. The codebase is modern (React 19, TypeScript, Vite) and includes comprehensive testing with Playwright. Architecturally, it operates as a client-side SPA with two views (edit and animate) and a toolbar for loading/playback/export.
Coral is an open-source, multi-tenant comment moderation platform developed by Vox Media. It provides a full-stack application with embedded commenting widgets (stream), a comprehensive admin panel for moderation, configuration, and community management, an authentication system supporting local, OAuth2/OIDC, Google, Facebook, SSO, and account management pages. The system architecture consists of a Node.js/Express server with Apollo GraphQL, MongoDB for persistence, Redis for caching and pub/sub, and Bull for job queues. The client uses React with Relay for GraphQL data fetching, and is organized into several bundles: stream (the embeddable comment widget), admin, auth, account, install, count, and embed. The core data flow involves comments being submitted via GraphQL mutations, processed through a modular pipeline (spam detection, word list filtering, toxicity analysis via Perspective API, external moderation phases, and pre-moderation rules), stored in MongoDB, and then distributed via GraphQL subscriptions and notifications (email, Slack, webhooks). The codebase is extensive and well-tested, though it exhibits some legacy patterns (recompose HOCs, partial migration from class components to hooks, duplicated utility code between client and server scripts).
RetroAssembly is a full-stack web application for self-hosting a personal retro game collection and playing it directly in the browser via emulation. It provides a complete library management system for ROMs, save states, favorites, and launch history, with a rich UI built on React 19, Radix UI, and Tailwind CSS 4. The backend uses Hono with Drizzle ORM and SQLite (Node.js) or Cloudflare D1 (Workers), with file storage abstracted for local filesystem or Cloudflare R2. Emulation is powered by Nostalgist.js using libretro cores, supporting dozens of platforms with per-platform core options, BIOS validation, shaders, rewind, and auto-save. The app features multi-user accounts with shared library mode, keyboard/gamepad navigation via spatial navigation, a virtual gamepad for touch devices, internationalization with 12 languages, and a Docker-first deployment model. The architecture is dual-runtime (Node.js or Cloudflare Workers), with a Vite-based build system and pnpm workspaces. While the codebase is well-structured and demonstrates strong engineering patterns, it carries medium technical drift due to pinned CDN commit hashes, patched third-party packages for SSR compatibility, and the complexity of maintaining dual runtimes.
ListenBrainz Server is the backend and frontend for ListenBrainz, an open-source music listening history platform operated by the MetaBrainz Foundation. In production it ingests listening events from multiple sources (Spotify, Last.fm, Libre.fm, Maloja, file uploads, and direct API submissions), stores them in TimescaleDB, enriches them with MusicBrainz identifiers via an MBID mapping pipeline, and exposes them through a public REST API, a Last.fm-compatible API, WebSocket streams, and a React single-page application. The system also computes per-user and site-wide statistics, artist/recording/user similarity, collaborative-filtering recommendations, and annual 'Year in Music' summaries using Apache Spark batch jobs orchestrated through RabbitMQ and HDFS. The architecture is a hybrid of a traditional Flask web application and a set of background data-processing services. The main web server handles user authentication, API endpoints, playlist management, social features, and page rendering, while separate workers consume RabbitMQ queues for timescale writes, Spark job requests, metadata cache crawling (Spotify, Apple Music, SoundCloud, Internet Archive), and background imports/exports. The frontend is a large TypeScript/React application with React Router, TanStack Query, Jotai state, and a custom multi-source audio player called BrainzPlayer. Although the repository is primarily an application, it contains substantial data-engineering machinery—Spark incremental stats engines, dump generation/import, MBID canonicalization, and similarity algorithms—making it a genuinely hybrid codebase with the application character dominant. The codebase is well-structured for its size: it has clear module boundaries, abstract base classes for importers and OAuth services, a reusable incremental stats query-provider pattern, and extensive unit and integration tests. However, it also carries significant complexity and technical debt: multiple database backends, duplicated SQL across Spark entity stats, legacy compatibility endpoints, hardcoded external URLs, and some skipped or heavily mocked tests. The project is actively maintained, with a steady stream of schema migrations and feature additions through 2026.