ERPNext is a comprehensive open-source ERP (Enterprise Resource Planning) system built on the Frappe Framework. It provides a full suite of business management modules including Accounting, CRM, Buying, Selling, Stock/Inventory, Manufacturing, Projects, Assets, Quality Management, Support, and more. The system uses a metadata-driven architecture where DocTypes (document types) define data models, business logic, and UI behavior. The codebase follows a modular structure with each business domain in its own directory (accounts, buying, selling, stock, manufacturing, projects, etc.). It includes a modern React/TypeScript banking module built with Vite for bank reconciliation and statement importing. The system supports multi-company, multi-currency, multi-language deployments with extensive regional/localization support for tax compliance across many countries. It has a robust patch/migration system for database schema evolution and a comprehensive test suite.
libGDX is a mature, cross-platform Java game development framework supporting Windows, Linux, macOS, Android, iOS (via RoboVM), and web browsers (via GWT). The codebase is organized as a multi-project Gradle build with a core module (gdx) providing platform-agnostic APIs for graphics (2D/3D), audio, input, file handling, math, utilities, scene2d UI, asset management, and tile maps. Platform-specific backends implement these interfaces using LWJGL3 (desktop), Android SDK, RoboVM (iOS), GWT (web), and a headless backend for testing. Extensions provide Box2D (2D physics), Bullet (3D physics), FreeType (font rendering), and development tools (texture packer, particle editor, font generator). The architecture uses interface-based abstraction with platform-specific implementations, enabling write-once-run-anywhere game development. The codebase demonstrates strong engineering practices: clean separation of concerns, extensive test coverage (unit tests + integration tests across backends), native code integration via JNI/SWIG for physics engines, and a comprehensive asset pipeline. Recent commits (2026) show active maintenance with modern Gradle, Java 17+ compatibility, and ongoing MetalANGLE backend development for iOS.
This is a Laravel package that enables self-hosting of Google Fonts by fetching font CSS and asset files from Google's servers, storing them locally on a configurable filesystem disk, and serving them via Blade directives. The core logic resides in the `GoogleFonts` service class, which handles downloading, caching, and rendering fonts either inline or as external stylesheets with optional preload support. The package provides a fallback mechanism to load fonts directly from Google if local storage fails. It is well-tested with Pest and snapshot assertions, supports a wide range of Laravel versions (8–13) and PHP 8.0+, and follows Spatie's typical high-quality package structure with clean separation of concerns, config-driven behavior, and a dedicated Artisan command for prefetching fonts.
This is a Python library for quantitative finance, specifically portfolio optimization and risk management. It implements Conditional Value-at-Risk (CVaR) optimization using Benders decomposition, mean-variance optimization via quadratic programming, and entropy pooling for adjusting scenario probabilities under user-defined views and stress tests. The library also includes fully flexible resampling (FFR) for simulation, Black's model for option pricing, and a set of helper functions for financial statistics. It is designed as a monolithic Python package with a clean API, extensive tests (100% coverage), and 14 Jupyter notebooks that serve as reproducible examples. While the primary character is an application library, it has a strong research and educational orientation, referencing academic papers and providing walkthroughs. The code is well-structured, but domain-specific and depends on cvxopt with GLPK for linear programming, which may limit portability.
feishu-pages is a monorepo application that exports Feishu (Lark) wiki knowledge base to Markdown for static site generators. It consists of three workspaces: feishu-docx (a library for converting Feishu Docx documents to Markdown), feishu-pages (the main CLI tool that orchestrates the export process), and website (a VitePress documentation site). The CLI authenticates with the Feishu Open API, fetches wiki space structure, converts document blocks to Markdown, downloads and rewrites asset URLs, generates YAML frontmatter for static site generators, and outputs a structured directory of Markdown files with SUMMARY.md and docs.json for navigation. The architecture features clear separation of concerns with dedicated modules for API interactions, document processing, asset handling, and summary generation.
AssetOpsBench is a unified open framework for building, orchestrating, and evaluating domain-specific AI agents in industrial asset operations and maintenance (Industry 4.0). It provides a suite of MCP (Model Context Protocol) servers that expose domain tools for IoT telemetry, work order lifecycle, failure mode analysis, time-series forecasting/anomaly detection, vibration diagnostics, and utility functions. The framework includes multiple agent runners (plan-execute, Claude, OpenAI, Deep, Stirrup, OpenCode, direct LLM) that consume these tools, and a comprehensive evaluation pipeline with LLM-as-judge and deterministic structured-answer scorers. The system is designed to run reproducible benchmark scenarios with ground truth, producing leaderboard reports for agent comparison. It is accepted at KDD 2026 and powers multiple competitions. Architecturally, the system is a collection of Python packages with 14 CLI entry points defined in pyproject.toml. Each MCP server is a standalone FastMCP application using stdio transport, backed by CouchDB for persistence. Agent runners share a common trajectory model and observability layer (OpenTelemetry with file-based export). The evaluation pipeline is pluggable with a scorer registry. The codebase also includes a significant data/research component: a time-series feature extraction library (130+ extractors), a model catalog with foundation models (TinyTimeMixer, sktime wrappers), synthetic data generation for vibration signals, and showcase notebooks demonstrating end-to-end model lifecycle. The hybrid nature makes it both a software benchmark framework and a research platform for industrial AI.
The Video Autopilot Kit is a Python-based framework for automating the creation of vertical shorts (YouTube Shorts, Reels, TikTok) and long-form videos. It provides three isomorphic production lines (teaching long-form, vertical shorts, interview show) each built as a knowledge layer → mechanical gate → one-command driver. The system centers around an Editkin v4 durable workflow contract that serves as the single source of truth for planning, evidence binding, audit, atomic apply, and render. Key features include an image-first material system requiring verified source media, a unified filter library of 38 reusable presets, and privacy-first design that avoids storing personal data in the repository. The architecture is modular, with specialized modules for asset management, color grading, audio processing, motion assets, art direction, scene auditing, and quality assurance. Entry points include CLI-driven pipelines for shorts (`src/shorts_autopilot.py`), interviews (`src/interview_autopilot.py`), long-form (`src/longform_maker/`), publishing (`src/publish_hub_cli.py`), and competitor teardown (`src/teardown.py`). The system relies on external tools like `ffmpeg`/`ffprobe` for video processing and optional OCR libraries for competitor analysis, with cross-platform compatibility handled via `src/platform_compat.py`. Despite its strengths, the kit faces maintenance challenges due to hardcoded assumptions about directory structures and platform specifications, as well as dependency drift risks from external tools like ffmpeg and OCR libraries. However, the inclusion of a release manager and self-updater helps mitigate some of these risks by providing deterministic builds and update mechanisms.
This repository is a desktop application for game content creation, specifically designed for a Genshin Impact-like game. It provides a node-based visual scripting system (Graph Code) where users create logic using interconnected nodes representing game functions (combat, skills, UI, etc.). The application features a PyQt6-based GUI for graph editing, resource management, and previewing, along with automation capabilities for OCR, screen capture, and input simulation to interact with the editor. It includes a robust validation engine to ensure graph correctness, a layout engine for auto-arranging nodes, and export pipelines to produce game-ready formats (.gil and .gia). The architecture is monolithic with distinct modules for the GUI (app/ui/), automation (app/automation/), core engine (engine/), and CLI tools (app/cli/ and private_extensions/ugc_file_tools/). Key entry points are the main GUI launcher (app.cli.run_app), validation CLI (app.cli.graph_tools), and the unified UGC tools CLI (private_extensions/ugc_file_tools). Data flows involve graph creation/editing, validation, layout, export/testing, and automation-driven interactions. External dependencies include PyQt6, RapidOCR (onnxruntime), OpenCV, Pillow, and keyboard/mouse libraries for automation.
BundleMaster is a Unity asset management system for handling AssetBundles with synchronous/asynchronous loading, reference counting, and hot-update capabilities. The architecture consists of core runtime components (BundleMasterRuntime/), platform-specific adapters (WebGL, Nintendo Switch), editor tools for configuration and building, and utility systems for threading and cryptography. Key entry points include AssetComponent.Load()/LoadAsync() for asset loading, AssetComponent.Initialize() for bundle setup, and AssetComponent.Update() for maintenance. The system manages asset lifecycles through reference counting and periodic unloading pools, supports encrypted/obfuscated asset bundles, and provides editor workflows for building asset bundles with version tracking.
Polymod is a Haxe library that enables modding for games and applications by intercepting asset loading and providing a runtime scripting system. It supports multiple game engines (OpenFL, Lime, HEAPS, NME, Flixel, and custom backends) through a clean abstraction layer of backends and file systems. The core API (Polymod.init, scan, loadMod) allows developers to define mod root directories, load mod metadata, and apply asset replacements, text merges (XML, JSON, CSV, TSV), and script modifications. A notable feature is the integrated HScript interpreter (a fork of the language) that allows mods to define classes, override methods, and extend game logic at runtime. The codebase is well-structured with clear separations of concerns (backends, file systems, format parsers, utilities) and includes extensive sample projects demonstrating integration with various frameworks. However, it lacks a formal test suite, contains some debugging artifacts (trace calls), and relies on heavy macro metaprogramming for scripted class generation, which increases maintenance risk across Haxe compiler versions. The dependency on Lime/OpenFL internals and platform-specific conditionals makes the code somewhat brittle, though the core abstractions remain reusable.