Yet Another Surge Dashboard (YASD) is a React 19 single-page application for managing and monitoring Surge network proxy instances through their HTTP API. The application provides a web-based interface to configure Surge instances, view network traffic statistics, manage profiles and rules, and inspect request logs. Built with a modern tech stack including Vite, TypeScript, Redux Toolkit, SWR for data fetching, and shadcn/ui for components, it features internationalization (English/Chinese), mobile responsiveness, and PWA capabilities. The architecture follows React best practices with clear separation of concerns between components, hooks, state management, and API layers.
Tokimeki is a full-featured, open-source Bluesky client built with SvelteKit and TypeScript. It provides a multi-column deck layout (similar to TweetDeck) with support for multiple accounts, real-time timeline updates, chat (direct and group), rich media embeds, custom moderation (keyword mutes, labelers), and extensive customization (themes, keyboard shortcuts, layout options). The application uses the AT Protocol (XRPC) for all Bluesky interactions, implements OAuth and password-based authentication, and includes a service worker for push notifications and offline caching. Architecturally, Tokimeki is a single-page application (SPA) with server-side routes for OAuth flows, AI features (alt text generation, column icon suggestions), and proxy endpoints. State management is handled via Svelte 5 runes ($state, $derived) and custom reactive classes (ColumnState, AppState, PostState). Data persistence uses IndexedDB (via Dexie) for accounts, bookmarks, and drafts, and localStorage for settings. The codebase is modular with clear separation of concerns: UI components in src/lib/components/, state classes in src/lib/classes/, utilities in src/lib/, and routes in src/routes/. It includes a comprehensive test suite using Vitest and Playwright. Key features include a custom feed merge engine for combining multiple timelines, a virtual scrolling system with Fenwick tree for efficient rendering, an image compression pipeline with WebAssembly and fallback, a full chat system with group management, and an atmosphere service registry for third-party integrations. The application is internationalized with 10+ locales and supports on-device translation via the browser's Translator API.
LiveSplit One is a cross-platform speedrun timer application, the successor to the classic LiveSplit timer. It runs as a Progressive Web App and as a Tauri desktop application, targeting Windows, Linux, and macOS. The core timing logic is compiled to WebAssembly via the 'livesplit-core' Rust library, while the UI is built with React 19, TypeScript, and Vite. The application provides a rich set of features for speedrunners: highly customizable split timers, real-time comparisons, layout editor with drag-and-drop, integrated leaderboards from Speedrun.com, global hotkeys (desktop only), always-on-top mode, WebSocket server for remote control, and support for multiple timekeeping methods (real time vs game time). Data persistence is handled via IndexedDB in the browser and the filesystem in Tauri. The codebase is well-structured with a clear separation between core logic (WASM), UI components, and platform-specific code, though some central components like 'LiveSplit.tsx' are large and could benefit from further decomposition.
OS1 (nokodo) is a full-stack AI-powered collaborative platform combining autonomous agents, deep research, real-time collaboration, and extensible tooling in a self-hostable workspace. The system features a modular architecture with FastAPI/Python backend, Svelte 5 frontend, and separate admin console, communicating via REST API, WebSocket, and Redis pub/sub. Core capabilities include AI agent construction with tool integration (web search, code execution, file operations), persistent memory system with vector search, real-time document editing, and comprehensive resource management (threads, notes, files, projects, calendars, reminders). The platform emphasizes extensibility through plugin systems for tools, filters, and hooks, with production-ready deployment via Docker Compose.
This repository implements a curated directory of Chinese-language Telegram channels, groups, and bots. It combines a Python-based data pipeline (scraping, filtering, categorization, and README generation) with a modern Astro static site that provides search, category browsing, and PWA features. The system ingests links from multiple sources (existing README, tg-nav, GitHub Issues), applies strict filtering rules (language, harmful keywords, subscriber thresholds), and outputs both a human-readable README and a structured JSON consumed by the frontend. The architecture is a hybrid of data engineering and web application, with the data pipeline being the core value proposition. The frontend is well-crafted with SEO, analytics, offline support, and a clean UI. The codebase demonstrates solid engineering practices, including reusable filtering logic, component-based UI, and automated build steps.
ReadAny is a full-featured, cross-platform e-book reader application with deep AI integration. It supports reading EPUB, PDF, MOBI, FB2, and other formats via the modified foliate-js engine, and provides text-to-speech, annotations, reading statistics, and cross-device sync (WebDAV, S3, LAN). The AI subsystem offers chat with RAG (semantic search over book content), context-aware tools, and execution of user-defined skills. The application follows a local-first architecture with robust offline capabilities and optional cloud sync. The codebase is structured as a pnpm monorepo with four main packages: 'core' (shared business logic, types, stores, AI, RAG, sync, stats, TTS), 'app' (Tauri desktop client with React+shadcn UI), 'app-expo' (Expo/React Native mobile client), and 'cli' (agent integration via MCP and managed shims). The application exhibits high craftsmanship in its platform abstraction layer, persistent store pattern, and hybrid search engine. However, there is significant platform-driven code duplication (desktop vs. mobile UI components) and a complex dependency graph with multiple patched packages, indicating some architectural debt.
This repository is a starter template for Nuxt 4 applications, created by Anthony Fu. It provides a pre-configured setup with modern tooling including Vue 3, Vite, UnoCSS for atomic CSS, Pinia for state management, PWA support via @vite-pwa/nuxt, and auto-imports for composables and components. The architecture follows Nuxt's file-based routing and SSR model, with a Nitro server layer for API endpoints (e.g., a simple pageview counter). The codebase demonstrates clean, idiomatic usage of Nuxt 4 features like `useState`, `useFetch`, layout system, and the Composition API. It is not a production application but a foundation for building Nuxt projects, with several reusable configuration modules and composables.
Solar Wanderer is a browser-based 1:1 real-time solar system explorer powered by NASA JPL ephemerides. Built with Three.js 0.165 and Vite 5, it renders the entire solar system at true scale (0.5m to 1e15 km) using a floating-origin world engine, logarithmic depth buffer, and Keplerian orbital mechanics. Users can seamlessly fly through space, walk on planetary surfaces (including real DEM terrain for Earth, Moon, Mars), dive into Earth's oceans, or orbit from a Google Earth-style camera. The application includes a bilingual (Chinese/English) interface with 7-language i18n, search, guided tours, educational facts with NASA sources, mobile touch controls, and shareable URLs. All ephemeris data—planets, 21 moons, 28 TNOs, 4 comets, and ~5400 small bodies—is generated offline via scripts that fetch from NASA JPL and fitted to Horizons state vectors. The architecture is a client-only SPA with modular ES modules; no backend, no registration, no cookies. The codebase demonstrates high craftsmanship in its floating-origin precision, pure-function ephemeris, procedural terrain generation, and real-time atmosphere scattering, though it carries technical debt from a monolithic main.js and incomplete i18n for half its languages.
This Rails 8.0 monolithic web application serves as a conference scheduling and attendance management platform, specifically built for the Rails World conference. It allows authenticated users to browse an agenda of sessions (talks) sorted by time and location, bookmark sessions to create a personal schedule, and receive proactive reminders via email and web push notifications. Administrators manage conferences, sessions, speakers, locations, and tags through the integrated Avo admin panel. The app also supports PWA installation, guest browsing of public sessions, and a profile system with social links and QR code sharing. Under the hood, the application leverages Hotwire (Turbo + Stimulus) for a responsive, single-page-like experience without a JavaScript framework. Background jobs are handled by SolidQueue with a separate SQLite database, including recurring tasks for session reminders and Litestream backup verification. Notifications are implemented using the Noticed gem with custom web push delivery. The authentication system uses bcrypt and includes password reset flows; authorization is managed via ActionPolicy. The codebase is thoroughly tested with RSpec including system tests using Cuprite, and includes a comprehensive CI pipeline with linting (RuboCop, ERB Lint, StandardJS), security scanning (Brakeman, bundler-audit), and code quality checks (RubyCritic, DatabaseConsistency). While not a generic SaaS, the architecture is clean and follows Rails conventions closely. Several components (form builder, query object, feature flag module, custom notification delivery) are well-isolated and demonstrate patterns that could be extracted into other Rails projects. The use of SQLite with Litestream replication and Kamal deployment reflects a modern, low-ops approach to hosting.
IT-Tools is a single-page application (Vue 3 + TypeScript + Vite) that provides a curated collection of over 80 client-side developer utilities. These utilities include hashing, encoding, formatting, conversion (JSON, YAML, TOML, XML, etc.), crypto (JWT, RSA, bcrypt), network tools (IP subnet calculator, MAC address lookup), text manipulation, and many others. All processing occurs entirely in the browser; there is no backend. The app is a monolith with lazy-loaded per-tool routes, using a custom UI component library (c-*) alongside Naive UI, Pinia for state, vue-i18n for translations, and VueUse composables. It is containerized (Docker) and can be self-hosted or used via the hosted version on Vercel/Netlify. The repository demonstrates a strong convention for tool definition, testing, and internationalization, though tool quality varies. It is not a data research or analytics project.
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.
Floorp is a Firefox-based browser that extends Gecko with a comprehensive feature layer including workspaces, split-view tiling, panel sidebar, PWA/SSB management, mouse gestures, keyboard shortcuts, command palette, tab stacks, design theming, private containers, external browser integration, notes, profile manager, and more. The architecture is hybrid: chrome components are built with SolidJS and injected via a custom loader into Firefox's XUL, while settings, new tab, notes, welcome wizard, and profile manager pages are standalone React/Vite web applications served within the browser. Configuration is stored in Firefox preferences with io-ts runtime validation, and cross-process communication uses a birpc bridge. The build system is Deno-based, orchestrating Vite builds, Firefox runtime patching, and platform-specific packaging (macOS App Shim in C++, Windows Tauri stub installer). The codebase demonstrates strong engineering practices with extensive test coverage (colocated browser tests, unit tests, integration tests), clean reactive state management patterns, and well-structured feature modules. However, it carries technical debt from multiple legacy migration paths, duplicated UI components across page apps, and tight coupling to Firefox internal APIs that require version-specific workarounds.
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.
DevDocs is a web application that aggregates and serves API documentation for hundreds of programming languages, frameworks, and tools in a unified, searchable, offline-capable interface. The backend is a Ruby/Sinatra server that provides the static assets and a minimal API, while the frontend is a custom JavaScript single-page application with client-side search, keyboard navigation, and a service worker for offline access. The core data generation pipeline consists of Ruby scrapers that fetch documentation pages from official sources, apply a chain of filters (HTML cleaning, entry extraction, URL normalization, image optimization), and produce normalized JSON indexes and cached pages stored on disk. The architecture is largely monolithic with a strong separation between the scraping pipeline (lib/docs) and the frontend (assets/javascripts). While primarily an application, it contains a substantial data engineering component in its scraper/filter system, which is reusable and generalizable for other documentation aggregation projects.
Carbon is a Next.js web application for creating and sharing beautiful images of source code. It provides a CodeMirror-based editor with extensive customization: syntax themes (30+ built-in), fonts (13 options), background colors/images (including Unsplash integration), window themes, padding, shadows, and line numbers. Users can import code via paste, file drop, or GitHub Gist URLs. Export options include PNG/SVG at multiple resolutions, clipboard copy, Twitter sharing, Imgur upload, and embed codes. Saved snippets persist via Firebase authentication with automatic Twitter/Slack unfurling. The app runs as a PWA for offline use. Architecture is a Next.js 12 monolith with API routes for oEmbed and server-side image generation (Puppeteer/Chrome AWS Lambda). State is managed through URL parameters (with base64-encoded complex state), localStorage, and React state. The codebase demonstrates solid engineering with custom CodeMirror modes for 6 languages, a sophisticated theme builder, and well-encapsulated UI components.
Vitesse is an opinionated Vue 3 + Vite starter template created by Anthony Fu. It provides a pre-configured development environment with file-based routing, auto-importing of components and APIs, state management via Pinia, internationalization (i18n) with lazy-loaded locale files, PWA support, Markdown-as-Vue-components, and utility-first CSS via UnoCSS. The template uses static site generation (SSG) via vite-ssg and includes critical CSS extraction. It is designed to accelerate the setup of modern Vue applications by integrating a curated set of plugins and tools. The codebase is well-structured, with clear separation of concerns: pages, layouts, composables, stores, and modules. The i18n module demonstrates a reusable pattern for lazy-loading translations using Vite's glob imports. While the template is primarily a collection of configurations and boilerplate, it exhibits high craftsmanship in its integration choices and adherence to Vue 3 best practices.
This repository is a Spotify client web application that helps users track new releases from artists they follow. It provides a progressive web app (PWA) experience with offline support, allowing users to view, filter, and favorite releases grouped by date. Users can export their release list to CSV or create/update a Spotify playlist with selected tracks. The application handles Spotify authentication via OAuth 2.0 PKCE flow, fetches data from the Spotify Web API, and persists state locally using localForage. Built with React, Redux Toolkit for state management, and Redux Saga for side effects, the app features a modular architecture with reusable UI components, filtering system, and settings management.
Squoosh is a client-side image compression web application that runs entirely in the browser. Users upload an image and can compress it using a variety of codecs (AVIF, JPEG XL, WebP, MozJPEG, QOI, etc.) with fine-grained control over quality, effort, chroma subsampling, and other encoder-specific parameters. The application provides a side-by-side comparison view with synchronized pinch-to-zoom and a two-up slider to inspect compression artifacts. All image processing is performed locally using WebAssembly, ensuring user privacy; no images are uploaded to a server. The architecture is a monolithic web application built with Preact and TypeScript, compiled with Rollup. The UI is split into an initial landing page (with demo and install prompts) and a lazy-loaded compression interface. Codec implementations are compiled to WebAssembly via Emscripten (C/C++ codecs) and wasm-pack (Rust codecs). Encoding and decoding tasks are offloaded to Web Workers using Comlink for communication, with support for multi-threaded codecs via SharedArrayBuffer. A service worker provides caching and offline PWA capabilities. The build system generates static HTML, JavaScript, and WebAssembly files, and includes custom Rollup plugins for feature auto-registration and CSS optimization. Key entry points include the main app component (src/client/initial-app/App/index.tsx), the compression workflow (src/client/lazy-app/Compress/index.tsx), the service worker (src/sw/index.ts), and the static site generator (src/static-build/index.tsx). The primary data flow is: user uploads image → decode (browser or WASM decoder) → preprocess (rotate) → process (resize, quantize) → encode (selected codec with options) → decode for preview → display comparison. Each phase can be aborted via AbortController. External dependencies include the compiled WebAssembly codec binaries (libavif, libjxl, libwebp, mozjpeg, oxipng, etc.), which are built using Docker and pinned source tarballs. Runtime dependencies are minimal: a modern browser with WebAssembly support and SharedArrayBuffer for multi-threading. The build toolchain requires Node.js, Emscripten, Rust/wasm-pack, and Docker.
Nextflux is a modern RSS reader client designed for the Miniflux server. It is a single-page application built with React 19, Vite 6, and TailwindCSS 4, featuring a three-pane layout for browsing feeds, articles, and reading content. The application emphasizes offline capabilities through IndexedDB storage via Dexie, allowing users to read feeds without an internet connection. The architecture employs a decentralized state management approach using Nanostores, with separate stores for authentication, settings, feeds, articles, and synchronization. Data persistence is handled through a repository pattern over Dexie, providing typed access to IndexedDB collections. The application synchronizes with the Miniflux server via a background sync service that handles incremental updates, conflict resolution, and optimistic UI updates. Additional features include a global audio player for media attachments, AI-powered article summarization, and extensive customization options through a settings panel. Notable reusable components include a utility library for class merging and helper functions, a dynamic font loading hook, and a custom hook for detecting reduced motion preferences. The UI is built upon a migrating component library (transitioning from HeroUI/Radix to @base-ui/react and then to a Luma/shadcn-based system), demonstrating a commitment to modern UI practices. The codebase exhibits strong modularity and separation of concerns, with clear boundaries between UI, state management, data access, and service layers.
VoucherVault is a self-hosted Django web application for digitally managing vouchers, gift cards, coupons, and loyalty cards. It provides a full CRUD interface with features like barcode/QR code scanning, expiry notifications via Apprise, multi-currency support via Fixer.io, offline-first capabilities (service worker + IndexedDB sync), OIDC authentication, item sharing between users, and a PWA manifest for mobile installation. The architecture is a monolithic Django app with Celery for background tasks (expiry checks), Redis as a message broker, and optional PostgreSQL or SQLite databases. The frontend uses the NiceAdmin Bootstrap template with custom dark mode and charting via ECharts. The codebase is well-organized with clear separation of concerns (models, views, forms, templates, static assets) and includes internationalization for English, German, French, and Italian. While the application is feature-rich and actively maintained, it lacks automated tests and has some code duplication in templates, which limits its quality score.