NodeNetwork is a .NET C# WPF library that provides a fully interactive node graph editor component, following the Model-View-ViewModel (MVVM) pattern with ReactiveUI and DynamicData for reactive data flows. The core library (NodeNetwork) offers view models and custom WPF controls for managing networks of nodes, connections, endpoints, port rendering, pan/zoom, and validation. The NodeNetworkToolkit extends this with higher-level abstractions including typed value nodes, node grouping into sub‑networks, a searchable context menu, breadcrumb navigation, and a force‑directed layout engine for automatic graph arrangement. Three example applications demonstrate practical usage: a simple arithmetic calculator, a Lua code generator, and a GLSL shader editor with a 3D OpenGL preview. The architecture is modular: the core library is decoupled from the toolkit and examples via view registration (NNViewRegistrar) and dependency injection via Splat. All viewmodels are ReactiveObjects, and views implement IViewFor<T>, allowing clean separation and testability. The repository is well‑tested with unit tests covering network validation, value propagation, and UI interactions. Despite its solid design, the codebase shows signs of technical drift: it targets .NET Framework 4.7.2 and .NET Core 3.1 (not the latest .NET), uses the deprecated OpenTK library for the shader editor, and has inconsistent NuGet reference formats (packages.config vs. project‑file references). Some view logic remains in code‑behind files, and nullable reference types are not enabled. The library is nonetheless actively maintained (last commit April 2026) and has a strong user base (962 stars). It is not a data research repository; it is a UI library with example applications.
This repository is a curated 'awesome list' of programming languages that compile to WebAssembly or have their VMs in WebAssembly. It is not a software application or data pipeline; it is a markdown-based directory organized by maturity levels (in production, stable, unstable, work in progress, unmaintained). The README.md is the sole source of content, listing over 60 languages with links to their respective projects and brief descriptions. The repository includes standard community files (CODE_OF_CONDUCT.md, CONTRIBUTING.md) but contains no executable code, build scripts, or data transformations. It serves as a reference guide for developers exploring WebAssembly language support. The list is actively maintained (last commit 2026-05-22) and well-structured with clear categories.
geometry3Sharp is a comprehensive C# library for 2D/3D geometric computing and triangle mesh processing. It provides a rich set of data structures (dynamic mesh, spatial indices, graphs) and algorithms (mesh editing, remeshing, simplification, boolean operations, distance queries, implicit surfaces, hole filling, smoothing, deformation). The library also includes I/O for common mesh formats (OBJ, STL, OFF), numerical solvers (sparse CG, SVD, eigen), and utilities like parallel loops and memory-efficient containers. It is designed for integration into real-time applications and Unity via conditional compilation. While the codebase shows signs of long development with some incomplete features and deprecated APIs, it remains a powerful and well-crafted tool for geometry processing tasks.
Perfolizer is a .NET performance-analysis toolkit extracted from BenchmarkDotNet. It provides statistical estimators (quantiles, MAD, variance), significance tests (Mann-Whitney, Welch), and specialized data structures such as Rqq for efficient range quantile queries. The repository is organized as a main class library, a demo executable, and two test projects, with CI that builds, tests, and publishes NuGet packages. Despite being labeled experimental, the codebase is actively developed, versioned, and shipped as a NuGet package.
This repository contains a collection of Advanced Combat Tracker (ACT) plugins designed to enhance Final Fantasy XIV gameplay. The main components include SpecialSpellTimer for ability cooldown tracking, UltraScouter for combat information overlays, TTSYukkuri for text-to-speech alerts, and XIVLog for gameplay video capture. The architecture follows a modular plugin pattern with shared functionality in FFXIV.Framework, utilizing WPF and MVVM for UI components. The system integrates with game memory reading via Sharlayan, processes combat logs for real-time event detection, and provides user-configurable overlays and alerts.
This repository is a massive, multi-language collection of algorithmic problem solutions primarily from LeetCode, 剑指Offer (Sword to Offer), and Cracking the Coding Interview. It serves as a reference and study resource for coding interview preparation. The core content is organized by problem number and includes solutions in over 10 languages (Python, Java, C++, Go, TypeScript, Rust, etc.). A secondary component is a web application (Dockerfile, package.json) that likely powers the site at leetcode.doocs.org, providing a browsable interface for the solutions. The repository is actively maintained with frequent commits and a large contributor base, but the codebase is dominated by boilerplate solution files with high duplication and no automated testing. The architecture is a flat collection of independent solution files rather than a cohesive software application.
SoundFlow is a comprehensive .NET audio framework providing cross-platform audio processing, synthesis, MIDI handling, and security features. It features a modular architecture with components, modifiers, and analyzers that can be chained together to build audio applications. The framework supports audio playback/recording, real-time effects, MIDI sequencing, audio analysis, encryption, watermarking, and fingerprinting. It includes extensive platform-specific native libraries (MiniAudio, FFmpeg, PortMidi, WebRTC APM) built for Windows, Linux, macOS, iOS, Android, and FreeBSD. The repository includes numerous sample applications demonstrating various capabilities, from simple playback to complex security-enabled audio processing.
This repository is a curated, community-maintained 'awesome list' for the Blazor framework (a Microsoft .NET web UI framework). It aggregates and categorizes hundreds of external resources including sample projects, tutorials, libraries, videos, articles, podcasts, tooling, books, and community links. The main entry point is the README.md, which provides a structured table of contents with shields.io badges (GitHub stars, last commit, license) for each listed resource. The repository also contains yearly archives (2017–2024) tracking historical resources, a Component-Bundle-Comparison.md that compares 16+ Blazor UI component libraries, and a CONTRIBUTING.md with contribution guidelines. The repository itself contains no executable application code or data pipelines; it is purely a documentation/curation project that serves as a discovery and reference hub for the Blazor ecosystem. The curation methodology follows a consistent pattern of categorization, metadata badges, and archival, making it a reusable template for other awesome lists. The repository is actively maintained with recent commits referencing .NET 11 previews in 2026, though the sheer volume of external links introduces inherent risk of link rot and staleness for less popular entries.
This repository is a comprehensive IoT device driver library for .NET nanoFramework. It provides bindings for hundreds of sensors, actuators, displays, and communication modules (e.g., BME280, SSD1306, NFC, Modbus, cellular modems, GPS). The architecture is a collection of independent driver projects, each with its own samples, tests, and documentation. Shared utility libraries (e.g., System.Device.Model, NumberHelper, SpanByte compatibility shims) support cross-cutting concerns. The codebase is actively maintained with frequent commits, but the sheer number of drivers (300+) leads to varying quality, some code duplication (e.g., SpanByte classes in multiple locations), and partially auto-generated code. Networking components like DHCP server, DNS server, and Home Assistant MQTT integration extend the library beyond raw sensor access. The primary use case is building embedded IoT applications on microcontrollers (ESP32, STM32) running nanoFramework.
TSforge is a CLI utility that directly manipulates the Windows Software Protection Platform (SPP) physical store to achieve permanent activation or extended evaluation periods for Windows Vista through 11 and associated add-ons (e.g., ESU). The codebase is a well-structured C# application targeting .NET Framework 3.5, consisting of a library (LibTSforge) and a command-line entry point (TSforgeCLI). It implements multiple activation methods (KMS4k, AVMA4k, ZeroCID) and modifiers for resetting grace periods, clearing tamper flags, and installing generated product keys. The architecture involves decrypting the encrypted physical store file, parsing its block-based structure, inserting new activation data (timers, bindings, HWID blocks), re-encrypting, and writing back while managing the SPP service. The code demonstrates deep reverse engineering of Windows licensing internals, with careful handling of different store formats across OS versions. Despite targeting a deprecated .NET version and using legacy cryptographic primitives (SHA1, RSA PKCS#1 v1.5), the code remains functional for its niche purpose.
Watt Toolkit (Steam++) is a cross-platform desktop application that serves as a multi-functional game toolbox primarily for Steam users. The system provides network acceleration via a local reverse proxy (YARP-based) with HTTPS interception, DNS analysis, and multiple proxy modes (Hosts, System, PAC, VPN, DNS intercept). It includes plugins for Steam account switching, two-factor authenticator management (import/export/recovery), game library management, ArchiSteamFarm integration for card farming, and game tools. The architecture is a modular plugin system built with Avalonia UI, .NET, and ReactiveUI, using a multi-process IPC model for privilege separation. External dependencies include WinDivert for Windows packet interception, XunYou SDK for game acceleration, and ArchiSteamFarm for automated Steam actions. The codebase demonstrates a complex but functional architecture with significant platform-specific code and some areas of technical debt.
SnapX is a cross-platform screenshot and screen recording tool, forked from ShareX, with extensive upload capabilities to dozens of services (image hosts, file storage, pastebins, URL shorteners). It features image effects (adjustments, filters, manipulations), OCR via PaddleOCR, QR code generation/scanning, hotkey automation, and clipboard monitoring. The application is built with Avalonia UI and .NET 10, targeting Linux, Windows, macOS, and FreeBSD. It includes a CLI, a native messaging host for browser integration, and a comprehensive settings system. The codebase is in early access with many features ported from ShareX but several stubs and incomplete implementations remain, particularly in screen recording, image annotation, and some uploaders. The architecture follows a core library (SnapX.Core) with separate UI (SnapX.Avalonia) and CLI projects, using MVVM pattern and dependency injection. While functional, the project exhibits significant technical debt and incomplete feature parity with its predecessor.
Apache Cordova CLI is a command-line tool for creating, building, deploying, and managing Apache Cordova-based mobile applications. It serves as a thin orchestration layer over the `cordova-lib` and `cordova-create` libraries, parsing user commands and delegating to those libraries for project management, platform/plugin operations, building, and running. The architecture is straightforward: a single entry point (`bin/cordova`) invokes `src/cli.js`, which uses `nopt` for argument parsing, then dispatches to appropriate functions (e.g., `create`, `platform`, `plugin`, `build`, `run`, `info`). The codebase is mature, well-tested, and actively maintained with CI, CodeQL, and license auditing. However, the CLI is tightly coupled to the Cordova ecosystem and offers no reusable components outside that context. The implementation is solid but follows standard patterns without exceptional craftsmanship.
HardDiskValidator is a Windows Forms application for testing hard drives for bad sectors and verifying disk integrity. It provides multiple test modes: read-only scan, read + wipe damaged sectors + read, read + write + verify + restore (non-destructive), and write + verify (destructive). The application uses the DiskAccessLibrary.Win32 NuGet package for low-level physical disk access, requiring administrator privileges. It features a visual block map showing test progress and results, with logging and speed display. The code is well-structured with clear separation between disk I/O (DiskReader, DiskTester) and UI (MainForm, UIHelper). It targets multiple .NET frameworks (2.0, 4.0, Core 3.1) and includes ILMerge for single-file deployment. The repository is a single-project solution with no tests, but the core disk testing logic is robust and handles I/O errors gracefully.
OptimaJet.Workflow is a .NET workflow engine library designed for business process management and automation. It provides a core runtime for defining, executing, and persisting workflow schemes (process definitions) across multiple database backends including SQL Server, MySQL, PostgreSQL, Oracle, SQLite, and MongoDB. The engine supports multi-tenancy, version control of workflow schemes, and includes a visual HTML5 designer for creating workflows. It is architected as a library/framework layer, intended to be integrated into applications rather than running as a standalone service. The codebase demonstrates a hybrid architecture, combining modern .NET Core samples with legacy .NET Framework implementations using Windows Workflow Foundation (WWF). This duality is evident in the presence of both `OptimaJet.Workflow.Core` (modern) and `Other/WorkflowFoundation` (legacy) directories. The library relies heavily on the Provider Pattern for persistence, allowing developers to swap database backends via dependency injection. It also features a robust migration framework (FluentMigrator for SQL, custom scripts for MongoDB) to manage schema evolution, particularly around multi-tenancy support (`TenantId` columns). While the library offers solid engineering patterns like generic database abstraction (`DbObject<T>`) and async/await persistence, the codebase suffers from significant technical drift. It includes deprecated technologies such as `System.Workflow` and WCF, and sample applications rely on older versions of frameworks like ABP (v6.5.0) and .NET Core 2.2. The duplication of persistence logic across five different database providers increases maintenance overhead and the risk of schema drift between implementations.
OplusEdlTool is a cross-platform desktop application (Avalonia UI / .NET) for flashing, backing up, and managing Oplus (Oppo/OnePlus) Android devices in Qualcomm EDL (Emergency Download) mode. The tool provides a graphical interface for reading partition tables, backing up individual partitions, merging super partition images from JSON definitions (super_def.json), applying firmware patch files, and verifying file integrity via SHA checksums. It integrates with Qualcomm's fh_loader.exe for low-level device communication and supports Oplus-specific ROM formats (.ofp, .ops). The application stores working data in LocalApplicationData, generates XML partition reports, and includes comprehensive logging. It is bilingual (English/Chinese) and explicitly warns users about dangerous operations like flashing the persist partition.
Elib2Ebook is a .NET 10 application that downloads books from 60+ online libraries (Litres, MyBook, BookRiver, etc.) and converts them into standard ebook formats (EPUB, FB2, CBZ, JSON, TXT). It is a dual-deployment solution: a CLI tool and a Blazor web UI, both sharing a core domain and service layer. The architecture is a layered .NET solution with Domain, DomainServices, and per-site ExternalServices projects, using a reflection-based GetterFactory to auto-discover site adapters. The system handles site-specific anti-bot measures, authentication, and pagination, then normalizes content into a common domain model before passing it to format-specific builders.
WebGPU.NET is a .NET binding library for the WebGPU API, specifically targeting WebAssembly via Blazor. It provides a low-level P/Invoke wrapper generated from Emscripten's WebGPU C header, enabling GPU compute and rendering in browser-based .NET applications. The repository includes a code generator (WebGPUGen) that parses the C header using CppAst and emits C# structs, enums, handles, delegates, and P/Invoke commands. The generated library is packaged as a NuGet package (Evergine.Bindings.WebGPU) with MSBuild integration for native WebGPU support. A Blazor WebAssembly sample (HelloTriangleWasm) demonstrates basic triangle rendering using the deprecated WGPUSwapChain API. The project is part of the Evergine ecosystem and follows the organization's binding conventions, with CI/CD pipelines and a binding manifest. While the core library is functional and the generator is effective, there are signs of technical drift: the sample uses a deprecated API, the generator has hardcoded paths and a typo, and the binding is tightly coupled to a specific Emscripten version. The repository is maintained but not actively evolving, with recent scope reduction (removal of non-browser support).
GrasscutterCommandGenerator is a Windows Forms (.NET Framework 4.8) desktop application that serves as a comprehensive administration and command-generation tool for Grasscutter, a Genshin Impact private server emulator. It provides a GUI to generate and execute server commands (e.g., give items, teleport, spawn entities, set weather), edit server configuration files (gacha banners, drops, shops, activities), manage player accounts and permissions, and run a MITM proxy to intercept game traffic. The application is heavily data-driven, relying on embedded localized text files for game entity IDs and names, and uses Newtonsoft.Json for serialization. It supports multi-language UI (Chinese, English, Russian, Traditional Chinese) and integrates with a remote command plugin (gc-opencommand-plugin) for direct server interaction. The architecture is a monolith WinForms application with a tabbed page interface. The main entry point is Program.cs, which initializes the main form (FormMain) that hosts multiple pages (e.g., PageGiveItem, PageAvatar, PageQuest, PageProxy) and modal editors (FormGachaBannerEditor, FormShopEditor). A base class (BasePage) provides common lifecycle and command execution methods. The application communicates with the Grasscutter server via HTTP (OpenCommandAPI) and can also modify system proxy settings to redirect game traffic. External dependencies include the .NET Framework, Newtonsoft.Json (embedded), and Windows API calls for proxy and hotkey management. Key data flows involve loading game data from embedded resource files at startup, constructing command strings from user input, and optionally sending them to the server. The proxy module (Eavesdrop) captures and forwards HTTP/HTTPS traffic between the game client and server. The tool also supports importing/exporting player data in the GOOD (Genshin Open Object Description) format. While the codebase is functional and well-organized for its domain, it is tightly coupled to the Grasscutter server API and game data, requiring manual updates with each game patch. No automated tests are present, and the reliance on hardcoded data and Windows-specific features limits portability.
Shutdown Timer Classic is a mature Windows desktop utility, implemented as a .NET Framework 4.8 WinForms application, that lets users schedule a timed system power action such as shutdown, restart, hibernate, sleep, or lock. The primary entry point is Program.cs, which parses command-line arguments, installs global exception handling, and launches the main Menu form. The architecture is a classic single-process WinForms monolith: Menu.cs configures the timer, Countdown.cs renders the live countdown and manages the tray icon, Timer.cs owns the countdown state machine, and helper classes wrap Windows APIs for shutdown (ExitWindows.cs), sleep prevention (ExecutionState.cs), and single-instance enforcement (ApplicationInstanceManager.cs). User settings are persisted as JSON in %AppData%\Shutdown Timer Classic\settings.json, with version migration logic to handle upgrades. External dependencies are minimal: the .NET Framework, Newtonsoft.Json for deserialization, and direct P/Invoke calls into Windows system DLLs. There is no data pipeline, telemetry, or research component; this is purely an application. The codebase is reasonably well-structured for a desktop utility of this scope. It demonstrates craftsmanship in several isolated helper classes, particularly argument parsing, Windows API wrappers, and single-instance handling, which could be extracted into other Windows system-tool projects with little modification. However, the project carries legacy-platform drag: it depends on .NET Framework 4.8 and WinForms, has no automated test suite visible, and stores UI resources as large base64 blobs in .resx files, making icon changes noisy. The application is actively maintained, with packaging support for both MSIX (Microsoft Store) and legacy MSI, and uses GitHub Actions for CI. Overall, it is a solid, functional utility with a few genuinely reusable low-level components, but not an exemplary architecture to study.