wsldl is a Go CLI tool for managing Windows Subsystem for Linux (WSL) distributions. It serves as an advanced launcher and installer that can install distributions from rootfs tarballs or ext4 VHDX images, including HTTP download with caching, resumption, and SHA-256 verification. The tool provides subcommands for running commands in the WSL instance (with optional Windows-to-WSL path translation), backing up (tar, ext4 VHDX, registry export), cleaning (unregistering), configuring settings (default user, WSL version, terminal type, mount flags), and querying configuration values. It also integrates with Windows Terminal and Fluent Terminal as default terminals. The architecture follows a clean CLI monolith pattern in Go, with each subcommand implemented as a module using dependency injection for testability. The WSL and registry APIs are abstracted behind interfaces, allowing comprehensive unit tests via mock implementations on non-Windows platforms. Library packages for HTTP download, file operations (including transparent gzip), Windows console API, Windows Terminal configuration parsing, and CLI error handling are well-isolated and potentially reusable in other projects. While the core functionality is tightly coupled to Windows and WSL, the codebase demonstrates strong engineering practices: comprehensive test coverage, clear separation of concerns, proper error handling, and maintainable build infrastructure (Go modules, cross-compilation, CI/CD with GitHub Actions). The project is actively maintained with frequent commits and responsive issue triage.
GFast is a full-stack, modular admin panel built with GoFrame v2.10 and Vue3. It provides a RESTful API backend for managing users, roles, departments, menus, dictionaries, configuration, logs, and system monitoring. The architecture follows a layered pattern: API definitions (api/v1), controllers (internal/app/*/controller), business logic (internal/app/*/logic), data access objects (dao), and service interfaces. Authentication uses JWT (gfast-token) and authorization uses Casbin with RBAC. Caching is abstracted via gfast-cache supporting memory or Redis. The system includes a code generator, scheduled tasks, and an OpenAPI/Swagger endpoint. External dependencies include MySQL, Redis, Casbin, and ip2region for IP geolocation.
This is a favicon API service built with TypeScript, Hono, and Bun that fetches and serves website favicons. The application provides a single HTTP endpoint that accepts a domain parameter, discovers favicons from multiple sources (HTML link tags, web manifest, common locations), optionally falls back to Google's favicon API, processes images (resize/format conversion), and returns either the image or JSON metadata. It's designed to be stateless and deployed behind a caching layer (CDN or reverse proxy) for production use. The codebase demonstrates strong modular architecture with clear separation of concerns, proper error handling, security features like SSRF protection, and comprehensive test coverage.
Hugo NexT is a high-quality, elegant Hugo theme ported from the popular Hexo NexT theme. It provides a classic blog layout with four distinct schemes (Muse, Mist, Pisces, Gemini), dark mode support, and extensive customization options. The theme integrates multiple comment systems (Waline, Giscus, Utterances, etc.), search engines (Algolia, local), analytics (51La, Baidu, Google, Busuanzi), and sharing services. It features responsive design, i18n for multiple languages, and a rich set of shortcodes for notes, quotes, bilibili videos, music players, and mermaid diagrams. The architecture follows Hugo's template hierarchy with well-organized partials, shortcodes, and render hooks, making it easy to extend and maintain. The codebase demonstrates strong craftsmanship with clean SCSS organization, modular JavaScript, and comprehensive configuration options.
This repository contains two Go CLI tools: `wp2hugo` and `hugomanager`. `wp2hugo` is a production-grade migrator that converts WordPress XML exports into complete Hugo static site structures. It parses WordPress posts, pages, custom post types, taxonomies, comments, and media attachments, then generates Hugo content files (Markdown with YAML front matter), static assets, custom shortcodes (gallery, audio, video, parallax blur, Google Maps, catlist), partials (comments), Hugo configuration, RSS feed with preserved GUIDs, and Nginx redirect rules. It handles a wide range of WordPress shortcodes, Gutenberg blocks, embeds (YouTube, GitHub gists), footnotes, and media download with caching and retry logic. `hugomanager` is a companion tool for post-migration site management: it can analyze Bing backlinks, shrink images/audio, suggest URLs/descriptions/image alt text via OpenAI, convert absolute links to relative, move content with attachments into page bundles, and generate site summaries. The architecture is monolithic but well-modularized into internal packages (wpparser, hugogenerator, mediacache, hugomanager sub-packages). The codebase demonstrates strong Go engineering practices: comprehensive linting, CI/CD with goreleaser, unit tests, and structured logging. It is actively maintained with frequent releases and community adoption (25+ sites migrated).
mapcn is a React map component library and documentation site, not a data project. The product is a single-file MapLibre GL JS wrapper (`src/registry/map.tsx`) that exposes composable components such as Map, MapMarker, MapPopup, MapRoute, MapArc, MapGeoJSON, MapClusterLayer, and MapControls. It is distributed as a shadcn/ui registry: users run `npx shadcn add @mapcn/...` and receive copy-paste source code. The accompanying Next.js 16 app is a showcase and docs portal, rendering live examples, code samples, installation commands, and generated LLM-oriented content via routes under `/llm` and `/llms.txt`. Architecturally, the repo combines a library (registry JSON + map.tsx) with an application shell (Next.js App Router, Tailwind CSS v4, shadcn UI components). The map components use React contexts, portals, forwardRef/useImperativeHandle, and MapLibre style expressions to manage markers, popups, routes, arcs, GeoJSON layers, clustering, and hover states. Blocks under `src/registry/blocks/` demonstrate realistic use cases (analytics maps, store locators, logistics networks, uptime monitoring) with hardcoded sample data and external data sources like OSRM routing and Natural Earth GeoJSON. These demo blocks are primarily illustrations, not data pipelines. Maintenance is active, but the codebase has risks: the core map library is a ~3000-line monolith, the distributable JSON registry duplicates source files, and the stack is heavily bleeding-edge (Next.js 16, React 19.2.3, Tailwind v4). No automated tests appear in the repository. Overall it is a polished, effectively structured component library with a strong distribution model, but its craftsmanship is constrained by the single-file monolith and build fragility.
This repository is the official JavaScript/TypeScript client SDK for Centrifugo, a scalable real-time messaging server. It provides a robust, event-driven client (Centrifuge class) that manages persistent connections via multiple transports (WebSocket, SSE, HTTP stream, SockJS, WebTransport), handles token-based authentication and subscription authorization, and supports three subscription models: stream (standard channel), map (keyed data), and shared poll (polling with version tracking). The SDK also implements advanced features like automatic reconnection with exponential backoff, recovery from connection drops using offset/epoch, command batching for HTTP transports, and delta compression for efficient updates. The architecture is library-oriented with a clear separation of concerns: transport implementations are abstracted behind a common interface, the main client class manages connection state and dispatch ordering via a serial promise chain, and each subscription type extends a base class with its own state machine (stream, map three-phase, shared poll). The codebase is extensively tested with both unit tests (using a fake server) and integration tests against a real Centrifugo instance in Docker. The SDK is published on npm, supports CJS and ESM builds, and includes protobuf codec support. Notable patterns include a transport abstraction with dependency injection that allows easy addition of new transports, a serial dispatch chain ensuring ordered response processing, and a per-key publish debounce mechanism. The library is actively maintained with ongoing work on refactoring subscription types as documented in NEXT_MAJOR_SUBSCRIPTION_TYPES.md. The repository also demonstrates high craftsmanship in its comprehensive test coverage, graceful error handling, and careful handling of edge cases like stale tokens, network interruptions, and concurrent operations.
This is the official Moodle mobile app, a large hybrid application built with Angular 20, Ionic 8, and Cordova 13. It is a client for the Moodle LMS and talks to Moodle sites through Moodle web services. The application uses an offline-first architecture with per-site SQLite schemas, sync/cron services, prefetch handlers, and a file pool, allowing users to browse courses, participate in activities (assignments, quizzes, forums, SCORM, H5P, etc.), receive push notifications, and manage files while disconnected. The primary entry points are `src/main.ts`, the Angular root component `src/app/app.component.ts`, and lazy-loaded modules under `src/core/features/` and `src/addons/`. The app includes a custom Cordova plugin for secure storage, diagnostics, and install referrer tracking, plus a Behat plugin for acceptance testing. Although the repo is dominated by application code, it contains some data-adjacent artifacts: offline database schemas, xAPI statement support, and language-pack generation scripts; these are not research pipelines and are best understood as application infrastructure.
YTDLnis is a feature-rich Android application that serves as a graphical frontend for yt-dlp, enabling users to download video and audio from over 1000 websites. The app follows the MVVM architecture with Room database for local persistence, WorkManager for background download tasks, and a repository pattern for data access. It provides a comprehensive download management system including queue management, scheduling, format selection, metadata embedding, chapter splitting, SponsorBlock integration, and support for custom yt-dlp commands. The application also includes a built-in terminal emulator for advanced users, cookie management, YouTube PoToken generation, and an observe-sources feature for monitoring channels or playlists for new content. The codebase is well-organized into UI fragments, viewmodels, repositories, and utility classes, with extensive use of Kotlin coroutines and Android Jetpack components. While the app is actively maintained and demonstrates solid engineering practices, some modules like UiUtil.kt are monolithic and tightly coupled, and the heavy reliance on external tools (yt-dlp, FFmpeg, Python) introduces ongoing maintenance risks.
ACGTI (ACG Type Indicator) is a production-grade, open-source web application that delivers a personality quiz matching users to anime characters based on MBTI dimensions. The frontend is a Vue 3 SPA with TypeScript, Vite, and vue-router, featuring 39 Likert-scale questions, 8 archetypes, and over 100 curated characters with multilingual support (zh-CN, zh-TW, en, ja). The backend runs on Cloudflare Pages Functions with D1 database for anonymous statistics collection, AI-generated insights via Workers AI, and a cron worker for periodic stats snapshots. The codebase includes extensive offline analysis scripts (Python and Node.js) for weight calibration, probability simulation, and data validation, demonstrating a hybrid character with strong data engineering practices. The architecture is clean: frontend scoring engine is decoupled from backend, i18n is well-structured, and CI/CD pipelines enforce data integrity. While the project is actively maintained and uses modern tooling, some manual synchronization points (e.g., count constants, duplicate data sources) introduce minor fragility.
The system-monitoring-center is a Linux desktop application for real-time system resource monitoring and management. It provides a tabbed interface displaying CPU, memory, disk, network, GPU, sensors, processes, services, users, and system information. The application allows users to monitor performance metrics, manage processes and services, and view detailed hardware information through a modular architecture. Built with Python and Tkinter using the Sun Valley theme, the application follows a modular structure where each tab (CPU, Memory, etc.) implements a consistent interface (tab_gui, initial_func, loop_func). Core system data is gathered by the Libsysmon module via /proc, /sys, and system commands (dmidecode, lspci, etc.). The GUI features interactive charts, process/service management capabilities, and supports internationalization across 15+ languages. Configuration is managed through a version-aware system in Config.py. Key reusable components include Common.py for generic GUI utilities (sortable treeviews, search entries, charting canvases) and Config.py for persistent settings management. The application demonstrates good engineering practices with clear separation of concerns, active maintenance, and low technical drift despite Linux-specific dependencies.
This repository is a collection of Agent Skills for AI coding assistants (Claude Code, Codex, OpenCode) that enables them to interact with the Obsidian knowledge management ecosystem. It contains no executable application code; instead, it provides structured Markdown specifications that define how an AI agent should create, edit, and manage Obsidian vault files, including Markdown notes, JSON Canvas diagrams, and Obsidian Bases. The skills cover six areas: Obsidian Flavored Markdown (wikilinks, embeds, callouts, properties), Obsidian Bases (database-like views with filters and formulas), JSON Canvas (visual node/edge diagrams), the Obsidian CLI (vault management and plugin development), Defuddle (web page to clean Markdown extraction), and Knap (template rendering from JSON/CSV data). Each skill follows a consistent pattern of workflow, syntax reference, validation rules, and troubleshooting guidance. Architecturally, this is a pure documentation and configuration repository. Its value lies in the thoroughness and precision of its specifications, which include validation checklists, common pitfalls, and complete examples. It is a model example of how to define operational boundaries and capabilities for AI agents through structured documentation, rather than traditional software code.
This repository provides an ESP-IDF component framework (esp-openclaw-node, esp-openclaw-talk, esp-openclaw-room-node) for building IoT devices that connect to the OpenClaw gateway via WebSocket. It implements device identity (Ed25519), session persistence, command dispatch, and WebRTC audio (Talk). The room-node component adds a full voice-interactive display client with LVGL-based animated face, Canvas (image/A2UI rendering), camera snapshot, file access, and real-time diagnostics. The codebase includes multiple board-specific examples (M5Stack Tab5, Waveshare AMOLED, ESP-BOX-3, M5Stack Dial) that demonstrate reuse of the core components. Strong engineering practices are evident: extensive host-based unit tests (with fake SDK headers), CI pipelines that verify cryptographic signatures and component patches, firmware packaging with provenance manifests, and a component registry release process for versioned distribution. The architecture cleanly separates concerns via board adapter abstractions and config structs, making the core components reusable across different ESP32 hardware.
This repository provides a comprehensive VHDL language toolchain written in Rust, centered around a Language Server Protocol (LSP) implementation. It includes a lossless concrete syntax tree (CST) parser (`vhdl_syntax`), a semantic analysis library (`vhdl_lang`) with name resolution, type checking, and overload resolution, a standalone linter (`vhdl-lint`) with rule selection and auto-fix, a formatter, and a CLI for AST dumping. The architecture is modular, with separate crates for parsing, analysis, linting, and the LSP server, enabling reuse of components like the CST framework and diagnostic system. The codebase demonstrates high craftsmanship with extensive test coverage (including fuzzing and snapshot tests), code generation from a grammar model, and careful handling of VHDL's Latin-1 encoding and source positions. However, it suffers from a dual-parser architecture (the older hand-written parser in `vhdl_lang` coexists with the newer CST parser in `vhdl_syntax`), which introduces duplication and potential drift. Some VHDL-2019 features are partially supported, and the project tracks the latest Rust stable, imposing a high maintenance burden. Overall, it is a production-quality tool for VHDL developers, with several reusable components that could be extracted for other VHDL tooling projects.
gitcrawl is a Go-based CLI and library for ingesting GitHub repository data (issues, PRs, comments, reviews, code files, workflow runs) into a local SQLite database, then searching and analyzing that data offline. It exposes commands like `gitcrawl sync owner/repo`, `gitcrawl search issues`, and `gitcrawl code index`, with optional full-text code search. The architecture is a layered CLI: a command layer, a GitHub GraphQL/REST client with rate-limit guarding, a sqlc-generated SQLite data-access layer, and a small TUI built on bubbletea/lipgloss. It also includes a separate metrics store with strict database-ownership validation and idempotent writes.
atmoz/sftp is a Docker image that provides a production-ready SFTP server built on OpenSSH. At runtime, the container starts sshd with a chroot jail, forcing every user into their own home directory and restricting access to SFTP only. User accounts are provisioned from three sources: command-line arguments, the SFTP_USERS environment variable, and a mounted users.conf file. The entrypoint merges these definitions on first run, generates unique SSH host keys if none are mounted, and optionally executes custom scripts from /etc/sftp.d before launching sshd or passing through arbitrary commands. The core logic lives in two well-crafted Bash scripts. files/create-sftp-user parses compact user specifications (user:pass[:e][:uid[:gid[:dir1,dir2]]]), validates them with POSIX regexes, creates system users with optional UID/GID, sets plain or encrypted passwords, aggregates SSH public keys from .ssh/keys into a deduplicated authorized_keys file, and creates writable subdirectories. files/entrypoint handles configuration merging, first-run initialization, host key generation, and command passthrough. The sshd_config enforces secure defaults: no root login, no TCP forwarding, no X11, and internal-sftp with ChrootDirectory %h. The project includes a solid integration test suite (tests/run) using shunit2 that works with both Docker and Podman, exercising real SFTP sessions, key-based login, directory creation, custom UID/GID, and legacy config paths. CI workflows rebuild images daily to pick up OpenSSH security updates and run ShellCheck plus signature verification. The codebase is small, focused, and well-maintained, with no significant technical debt or security debt. It is a strong example of a purpose-built infrastructure container with clean shell scripting and meaningful test coverage.
This repository is a React component library (`@codegouvfr/react-dsfr`) that provides a complete implementation of the French government's Design System (DSFR) for modern web applications. It covers nearly all DSFR UI components (buttons, forms, navigation, modals, tables, etc.) and adds framework-specific integrations for Next.js (both Pages Router and App Router), Vite, and Create React App, including SSR support without flash. The library also ships a CLI tool (`npx react-dsfr`) that performs static analysis of a project's source code to generate an optimized CSS bundle containing only the DSFR components actually used, solving a common bloat problem in design-system integrations. Additionally, it provides a GDPR consent management system, i18n per component, MUI theming compatibility, dark mode, and a large set of SVG pictograms. The architecture is a typical React library: each component is a memoized, forwardRef-wrapped functional component using DSFR CSS classes via a `cx` helper. Build-time scripts parse the DSFR CSS into TypeScript constants (spacing, colors, breakpoints, class names) to ensure type safety and ease of use. The library avoids bundling all DSFR CSS in JavaScript; instead, it relies on the CSS being loaded from `node_modules` and optionally trimmed by the CLI. Notable internal patterns include a lightweight `StatefulObservable` for reactive state, a set of stable-callback hooks (`useConst`, `useConstCallback`) to avoid unnecessary re-renders, and a factory pattern for pictograms. While not a hybrid repo, its build pipeline demonstrates a unique approach to CSS-to-TypeScript code generation. The codebase is actively maintained with a comprehensive test suite covering both runtime behavior and build-script correctness. However, it carries some technical drift: it relies on a patched version of `@gouvfr/dsfr` (1.14.2), the pictograms are large inline SVGs that must be manually updated, and the CSS optimization script uses hardcoded component mappings that could diverge from future DSFR releases. Overall, it is a high-quality, production-grade library suitable for any French public service website built with React.
This repository is a curated list of awesome PHP libraries, resources, and useful tools. It is primarily a software application, specifically a web application, that provides a comprehensive collection of PHP-related resources. The application is well-structured, with a clear categorization of resources and a simple, easy-to-use interface.
This repository is a GNU Radio out-of-the-module (OOT) implementation of the LoRa physical layer. It provides a comprehensive set of signal processing blocks for transmitting and receiving LoRa signals, including channel coding (Hamming), interleaving, whitening, CRC, header processing, modulation, demodulation, and frame synchronization. The module is designed for use with GNU Radio 3.10+ and includes hierarchical blocks for quick assembly of transmitter and receiver flowgraphs in GNU Radio Companion or Python. It also features a simulation framework for performance evaluation (BER/FER vs SNR) and has been validated with USRP hardware and commercial LoRa transceivers. The code is modular, well-documented, and actively maintained, with recent updates adding support for lower spreading factors (SF 5-6) and improved soft-decision decoding.
Dante is a production-ready Astro theme for single-author blogs and portfolios. It provides a complete static site with dark/light mode, pagination, tag filtering, RSS feed, sitemap, SEO metadata (Open Graph, Twitter Cards), a subscription form, and a hero section. The architecture follows Astro's content collections pattern: Markdown/MDX files in `src/content/` are loaded via schemas defined in `src/content.config.ts`, rendered by Astro components in `src/components/`, and assembled into pages in `src/pages/`. Styling uses Tailwind CSS v4 with custom design tokens and a typography plugin. The theme is configured through a single `src/data/site-config.ts` file that controls navigation, social links, hero content, and newsletter settings. It integrates with `@astrojs/mdx`, `@astrojs/rss`, and `@astrojs/sitemap` for extended functionality. The codebase is well-structured, with clear separation of concerns, reusable components, and modern Astro practices (image optimization, pagination, content validation). It is not a library or framework but a template that can be forked and customized.