This repository is a GitHub template for bootstrapping Kotlin Android projects with a modern, opinionated build setup. It provides a multi-module structure (app, library-android, library-kotlin, library-compose) with pre-configured static analysis via detekt, CI/CD via GitHub Actions, and publishing to Maven Central. The codebase demonstrates best practices for Gradle Kotlin DSL, version catalogs, and precompiled script plugins. The sample modules include a simple factorial calculator to illustrate cross-module dependencies and testing patterns (unit, instrumentation, and Compose UI tests). While the template is not a production application itself, it serves as a solid foundation for new Android projects, emphasizing code quality and automation from the start.
This repository is a Visual Studio Code extension that provides a comprehensive file and folder icon theme using the Catppuccin pastel color palette. It offers icons for over 300 file types and numerous folder types, split across four flavor variants (Latte, Frappé, Macchiato, Mocha). The extension is built with TypeScript and modern tooling (tsup, pnpm, eslint), featuring a modular architecture with separate concerns for configuration, icon compilation, theme generation, and build scripts. Users can customize settings such as monochrome mode, specific folder icons, and custom associations via VS Code settings. The codebase is well-structured, actively maintained, and includes CI/CD pipelines, integrity checks, and preview generation scripts.
ChestShop is a mature Bukkit/Spigot/Paper plugin that enables players to create and operate shops using chests and signs. It provides a full economy-driven trading system: players place a sign on a chest to define a shop, set prices, and buy/sell items. The plugin handles shop creation, transaction validation, inventory management, and economic transfers, with extensive integration hooks for popular protection and economy plugins (Vault, Reserve, WorldGuard, GriefPrevention, PlotSquared, Lockette, etc.). The architecture is event-driven and modular, with a core plugin module and version-specific adapter modules to support Minecraft versions from 1.13 to 1.20.5. It uses a custom configuration system with annotations, a lightweight database layer (SQLite via ORMLite), and a comprehensive localization system supporting 40+ languages. The codebase is well-structured with clear separation of concerns, but carries technical debt from deprecated Bukkit APIs, manual database migrations, and tight coupling to many external plugin APIs.
Katbin is a pastebin service (pastebin/paste.rs-style) built on Cloudflare Workers with Hono, D1 (SQLite) via Drizzle ORM, and a Vite + React frontend styled with Tailwind CSS. It supports paste creation with syntax highlighting (highlight.js), markdown rendering, raw paste access, and configurable expiration. The service includes usage analytics with documented visitor limits, differentiated rate limiting (missing raw pastes are limited separately from existing ones), and admin routes that enforce authentication before executing any queries. Deployment is fully automated via GitHub Actions with separate production and staging environments, including D1 migration management through wrangler. The codebase demonstrates strong engineering practices: type-safe database access, careful analytics implementation with explicit visitor limit documentation, and security-conscious route design. The test suite covers API error handling, analytics edge cases, and rate limiting behavior.
FTorch is a production-stable Fortran library that enables direct coupling of PyTorch machine learning models to Fortran scientific codes without requiring a Python runtime. It provides a comprehensive Fortran interface to LibTorch (PyTorch's C++ backend) for tensor operations, model inference, automatic differentiation, optimizers (SGD, Adam, AdamW), and loss functions (MSE, cross-entropy). The architecture uses a three-layer design: Fortran modules with derived types (torch_tensor, torch_model, torch_optim) that call a thin C API (ctorch.h/ctorch.cpp), which in turn wraps LibTorch. This layered approach isolates Fortran code from C++ ABI changes and allows the library to be built as a shared or static library with CMake, supporting CPU, CUDA, HIP, XPU, and MPS backends. The library includes extensive examples covering tensor manipulation, simple neural networks, ResNet-18 inference, batching, multi-I/O, looping, multi-GPU, MPI parallelism, autograd, and full training loops. Unit tests use pFUnit and integration tests are built from examples, with CI testing across multiple compilers (gfortran, ifx, flang) and platforms. A Python utility package (ftorch_utils) provides model conversion (PyTorch to TorchScript) and validation. FTorch is published in the Journal of Open Source Software (JOSS) and is used in several HPC climate and fusion simulation codes (E3SM, CAM, ICON, UKAEA). The codebase demonstrates strong engineering practices: fypp code generation reduces boilerplate for multiple tensor ranks and data types, C interoperability is handled cleanly via iso_c_binding, and finalizers ensure automatic resource cleanup. However, there are some maintenance risks including reliance on fypp preprocessing, a large CI matrix, and the need to track LibTorch releases. A legacy API (torch_tensor_from_array_legacy) is still present but deprecated. Overall, FTorch is a well-crafted, domain-specific library that fills a critical gap for Fortran-HPC users needing ML integration.
This repository is the core runtime and management infrastructure for the WildFly application server (formerly JBoss AS). It provides a model-driven management interface accessible via CLI, HTTP, and native remoting, enabling configuration, deployment, security, logging, patching, and domain/standalone server lifecycle management. The architecture is modular, with subsystems (controller, server, host-controller, cli, elytron, logging, threads, etc.) built on JBoss Modular Service Container (MSC) for service lifecycle and dependency injection. Key entry points include the CLI (CommandContext, CommandLineMain), management interfaces (HTTP, native remoting), and server bootstrap (Main, BootableJar). Data flows center on management operations processed through OperationContext/OperationStepHandler, configuration persisted as XML, and deployments processed through a DeploymentUnitProcessor chain. External dependencies include JBoss MSC, JBoss Modules, Elytron security library, Aesh CLI framework, and various Java standard libraries. The codebase demonstrates strong engineering practices with extensive use of builder patterns, state machines, strategy patterns, and a comprehensive validation framework, though it carries some technical debt from deprecated APIs and version sprawl across multiple schema versions.
RSS-Bridge is a PHP web application that generates RSS, Atom, and JSON feeds for websites that do not natively provide them. The core architecture is a plugin framework: each of the 447 'bridges' in bridges/ extends BridgeAbstract (or FeedExpander/XPathAbstract/CssSelectorBridge) and implements collectData() to scrape HTML, consume JSON APIs, parse embedded JSON-LD/Next.js state, or expand existing feeds into a standardized item structure. A front controller (index.php) dispatches through a middleware pipeline (security, caching, basic/token auth, exception handling) to actions such as DisplayAction, FrontpageAction, ListAction, and FindfeedAction, then renders items via pluggable output formats (Atom, MRSS, JSON Feed, HTML, Plaintext, Sfeed). Both web and CLI request paths are supported, and the Docker deployment is production-ready with nginx + PHP-FPM and curl-impersonate for anti-bot evasion. The framework itself demonstrates solid engineering: a lightweight DI container, factory classes for bridge/format/cache discovery, a well-designed HTTP client layer with retry logic and CloudFlare detection, a standalone RSS 1.0/2.0/Atom/MediaRSS feed parser, systematic SEO/JSON-LD metadata extraction, and multiple cache backends (file, SQLite WAL, memcached, null) with TTL policies. PHPUnit tests cover feed parsing, format output snapshots, cache implementations, parameter validation, and BridgeImplementationTest enforces structural conventions across all bridges. The bridge base-class conventions (PARAMETERS arrays, contexts, detectParameters, throwClientException/throwServerException) are consistent and well-documented. The dominant weakness is inherent to the scraping domain: most bridges rely on brittle CSS selectors, undocumented APIs, or hardcoded endpoints that break as upstream sites change. Known issues visible in code include hardcoded API keys (Formula1, Giphy, Instructables, TwitterClient), deprecated/duplicate bridges (VkBridge states 'Does not work anymore'; Mozilla and Kernel BugTracker bridges defer to BugzillaBridge), logic bugs (Modrinth parameter key typo, GGDeals assignment-in-condition, Steam assignment-in-condition), a PHP 7.4 compatibility floor (EOL since 2022), and bundled Parsedown 1.7.4. The anti-bot arms race adds ongoing maintenance burden, and many low-traffic bridges appear effectively unmaintained. Overall, the core framework is a strong, extensible example of plugin-style feed generation architecture with genuinely reusable components; the bridge corpus is heterogeneous in quality, mixing well-crafted adapters with fragile scrapers. The project is actively maintained with recent commits, CI workflows, and a large contributor base.
Amber is a Rust-based compiler that transpiles a high-level, statically-typed programming language into shell scripts (Bash, Zsh, Ksh). It provides a modern language with features like functions, type inference, generics, optional arguments, failable types, imports, loops, range expressions, array operations, and a standard library for file system, text, HTTP, math, and environment operations. The compiler architecture is modular: a CLI entry point (src/main.rs) dispatches to subcommands (build, run, eval, check, docs, test). The compilation pipeline (src/compiler.rs) orchestrates tokenization via heraclitus-compiler, parsing into a typed AST, type checking with control-flow analysis, translation to an intermediate fragment AST, optimization passes (unused variable removal, ephemeral variable elimination), and final shell code generation with post-processing (e.g., shell syntax checking). The system supports multiple shell targets and generates version-specific code. The codebase is well-structured with procedural macros (meta crate) for keyword registration and context management, and a comprehensive test suite using snapshot testing (insta). While alpha quality, the engineering is serious and the architecture shows thoughtful design patterns.
pytorch-forecasting is a deep learning library for time series forecasting, providing implementations of state-of-the-art models such as Temporal Fusion Transformer, N-BEATS, N-HiTS, DeepAR, PatchTST, TiDE, TimeXer, and many others. Built on PyTorch and PyTorch Lightning, it offers a complete pipeline from data preprocessing (TimeSeriesDataSet, encoders, samplers) through model training (with GPU support, callbacks, hyperparameter tuning via optuna) to prediction and evaluation (point, quantile, and distributional metrics). The library supports multivariate forecasting, static and time-varying covariates, categorical features, and multiple targets. A major v2 refactoring is underway, introducing a new data module layer and simplified package interface, though the v2 API is explicitly marked as experimental and unstable. The codebase is well-tested with automated integration tests across all models and metrics, and employs a composition pattern for metrics (supporting weighting, aggregation, and distribution losses) and a layered architecture for models (base classes, package containers, building blocks).
pycdc/pycdas is a C++11 command-line toolchain for reverse engineering CPython bytecode. pycdc decompiles compiled .pyc files back into human-readable Python source; pycdas emits a detailed bytecode disassembly (with options like --show-caches and --pycode-extra). Version coverage spans Python 1.0 (1994) through 3.13, with the correct opcode semantics selected from the .pyc magic number at load time. The entry points are pycdc.cpp and pycdas.cpp, which are thin CLIs over the pycxx static library that owns marshal-format parsing (pyc_object.cpp, pyc_numeric.cpp, pyc_string.cpp, pyc_sequence.cpp), code-object extraction (pyc_code.cpp), and interpreter version detection (pyc_module.cpp). It also supports decompiling raw marshalled code objects via -c -v <version>. Decompilation loads the code object and interprets its bytecode on a virtual stack machine (FastStack with history snapshots) inside ASTree.cpp, reconstructing structured control flow (loops, try/except, comprehensions, with-blocks) and lowering it into an ASTNode tree for source emission. Opcode semantics are maintained as an X-macro include (bytecode_ops.inl) with explicit version ranges, and per-version opcode-name maps live in bytes/python_*_*.cpp. The module boundaries cleanly separate binary I/O (endian-aware PycBuffer/PycFile streams), object marshalling, disassembly, AST construction, and printing - although the decompiler core itself is a dense, version-conditional megafile. QA is the project's strongest asset. Roughly 200 .pyc fixtures spanning every Python major release (plus an xfail set for known-unfixed cases) are checked by tests/run_tests.py, which compares decompiler output to expected output as token streams rather than exact text - tolerating cosmetic whitespace differences while still catching semantic regressions. Linux and Windows CI run the suite, and scripts/pymultic, Dockerfile.pybuild, and a collection of Autoconf modernization patches make it possible to rebuild ancient CPython releases to regenerate those fixtures. Recent commits cover Python 3.13 opcode support, and the repository is actively maintained. Caveats: the 25-year version matrix forces heavily conditional decompilation logic, some mutable global state exists in ASTree, and unknown or future-modified opcodes degrade to partial output with an 'Unsupported opcode' warning. For its niche, it is the most complete open-source CPython decompiler available.
Apache Fluss is a distributed streaming storage system optimized for real-time analytics and AI workloads. It provides both log (append-only) and key-value (upsert) table semantics, with sub-second freshness and support for columnar formats via Apache Arrow. The system follows a two-tier server architecture: a coordinator server managing metadata, rebalancing, and ACLs, and tablet servers handling data storage, replication, and snapshot management. It integrates deeply with Apache Flink (source, sink, catalog, tiering) and Apache Spark (catalog, read/write), and includes lake tiering to Iceberg, Hudi, Paimon, and Lance formats. A native Rust client with Python, Elixir, and C++ bindings provides multi-language access, and a stateless REST gateway is available. The codebase demonstrates strong engineering practices: a clean SPI-based plugin system for filesystems, metric reporters, authentication, and lake storage; a comprehensive exception hierarchy; thorough metrics and monitoring; full-text predicate pushdown; and sophisticated memory management with off-heap memory segments and paged output views. Configuration is modular with providers for files, directories, and environment variables. The project includes extensive unit, integration, and behavior tests for filesystems, replication, rebalancing, and Flink compatibility across multiple versions. Notable reusable components include the throwing functional interfaces for checked exceptions, a clean JSON serialization framework with versioned test patterns, and a memory management subsystem offering reusable memory segment pools. The system is production-ready, with active development, low known security alerts, and continuous integration across multiple OS and storage backends.
Tiling Shell is a GNOME Shell extension that provides advanced, customizable window tiling and management. It replaces the default window snapping with a flexible layout system where users can define custom tile arrangements (via a built-in editor or JSON files), use snap assist for precise placement, enable edge tiling with multiple modes (default, adaptive, granular), and auto-tile new windows. The extension also adds a panel indicator, keyboard shortcuts, window border customization with dynamic corner radius detection, and a window suggestions feature that proposes layouts after tiling. The architecture follows a manager pattern: per-monitor subsystems (TilingManager, ResizeManager, WindowBorderManager, RaiseTogetherManager) are created and destroyed by the main extension lifecycle. Communication is event-driven via GObject signals, with a central GlobalState singleton and a Settings wrapper around GSettings. The codebase is written in TypeScript, compiled for GJS, and supports GNOME Shell versions 42–50 on both X11 and Wayland. It includes a complex build pipeline that produces separate outputs for modern and legacy GNOME versions, along with full internationalization (10+ languages). While the extension is actively maintained and feature-rich, it relies heavily on private GNOME Shell APIs and contains version-specific workarounds, which introduces maintenance risk as the shell evolves.
graphql-hooks is a lightweight React GraphQL client library that provides a set of hooks for querying, mutating, and subscribing to GraphQL endpoints. It is designed as a minimal yet feature-rich alternative to Apollo Client, with a focus on small bundle size (22.9 kB gzipped). The library is organized as a Lerna monorepo containing the core package (`graphql-hooks`), an in-memory cache (`graphql-hooks-memcache`), SSR utilities (`graphql-hooks-ssr`), and a Babel plugin for compile-time GraphQL query extraction (`babel-plugin-extract-gql`). In production, the system operates as a client-side GraphQL executor within React applications. The primary entry points are React hooks: `useQuery`, `useMutation`, `useManualQuery`, and `useSubscription`. These hooks internally use `GraphQLClient` to send HTTP or WebSocket requests, passing through an optional middleware pipeline. The client supports caching via a pluggable interface (defaulting to `graphql-hooks-memcache` with LRU eviction and TTL), automatic refetching after mutations, file uploads via the GraphQL multipart spec, and server-side rendering by pre-fetching query results and injecting initial state into the HTML. Key data flows begin when a React component calls a hook. The hook interacts with `GraphQLClient`, which applies middleware (e.g., Automatic Persisted Queries or custom interceptors) before sending the request. Responses are cached and returned to the component. Mutations can optionally trigger refetches of related queries via an event emitter. The architecture promotes separation of concerns via middleware, a clean cache API, and support for multiple transport layers (HTTP, WebSocket, Full-WS). External dependencies include React (peer), `graphql-ws` or `subscriptions-transport-ws` for subscriptions, and `formdata-node` for file uploads in Node environments.
This repository is the source and build system for the multi-language edition of the classic computer science textbook *Structure and Interpretation of Computer Programs* (SICP). It contains the full text, exercises, and code snippets in XML, organized by chapter and section, for the original Scheme version as well as modern adaptations in JavaScript and Python. The build toolchain, implemented in TypeScript and JavaScript, parses the XML into multiple output formats: PDF (via LaTeX), a static HTML web edition, a JSON edition for the interactive Source Academy frontend, Markdown, and standalone program files. The system handles cross-references, code snippet extraction with dependency resolution, figure inclusion, index generation, and search index construction. The repository also includes CI/CD pipelines for testing generated programs against actual language runtimes (Node, CPython, MIT Scheme) and deploying the web edition to GitHub Pages. Additionally, AI-generated chatbot knowledge base modules for the Python edition are checked in. The codebase is well-structured with a clean edition abstraction and a modular processing pipeline, though it is tightly coupled to the SICP XML schema and the Source Academy ecosystem.
This repository is a Python library and command-line tool for extracting structured data from HTML documents. It supports multiple formats including W3C HTML Microdata, JSON-LD, Microformat, Open Graph, RDFa, and Dublin Core. The project provides a main extract function that runs all enabled extractors and returns the results in a dictionary, with an option to convert the output to a uniform JSON-LD-like structure for easier consumption. The architecture is modular, with each format handled by a separate extractor class. The main orchestration function in `_extruct.py` manages the extraction process, error handling, and result aggregation. The command-line interface allows users to extract data from a URL or file and output JSON directly. The project includes an extensive test suite with sample HTML files and expected outputs for each format, covering valid cases, edge cases, and invalid inputs. Key reusable components include the uniform output transformation module (`extruct/uniform.py`), which normalizes data from different formats into a common structure, and the error handling pattern used throughout the extraction pipeline. The project is actively maintained, with recent updates adding support for newer Python versions and maintaining compatibility with dependencies. Technical drift is low due to regular updates and a focus on compatibility.
TasmoAdmin is a web-based application for managing Tasmota-flashed IoT devices. It provides a responsive interface for device configuration, monitoring, firmware updates, and batch operations. The application features a modular PHP backend with dependency injection, factory patterns, and reusable helper utilities. It supports MQTT-based device discovery, automatic firmware updates via GitHub, and includes a self-update mechanism. The frontend uses Bootstrap 5 and jQuery for a modern user interface, with JavaScript modules handling dynamic interactions and state management.
Scopy is a cross-platform Qt/C++ desktop application for signal analysis and instrument control, developed by Analog Devices. It provides a software oscilloscope, spectrum analyzer, signal generator, logic analyzer, data logger, and many other test-and-measurement tools. The application communicates with Analog Devices hardware (M2K, AD936x, ADRV9009, etc.) via the IIO (Industrial I/O) framework and libiio, and integrates GNU Radio for real-time signal processing pipelines. Scopy features a modular plugin architecture where each hardware target or instrument is a separate plugin package, loaded dynamically at runtime. The core framework provides reusable GUI widgets (plotting, menus, docking), an IIO attribute abstraction layer (iio-widgets), an asynchronous command queue for device operations, and a JavaScript scripting API for automation and testing. The codebase is large and well-structured, with extensive CI/CD for Linux, macOS, Windows, Android, and ARM platforms, but contains some legacy code and mixed API styles that indicate moderate technical drift.
inletsctl is a CLI tool for automating the creation and management of inlets tunnel servers on various cloud providers. It provisions VMs with inlets-preinstalled via cloud-init, provides connection strings for clients, and supports deletion and Kubernetes port-forwarding. The application uses a modular Cobra-based architecture with provider-specific implementations abstracted through the cloud-provision package. Key functions include creating HTTPS/TCP tunnel servers, deleting cloud resources, downloading inlets binaries, and forwarding Kubernetes services to local machines.
This repository implements a Language Server Protocol (LSP) server for the Stimulus JavaScript framework, providing intelligent tooling for editors like VS Code. The architecture follows a standard client/server LSP pattern where the TypeScript-based VS Code extension (client) communicates with a TypeScript language server (server) via JSON-RPC. The server parses HTML, ERB, Blade, PHP, and JavaScript/TypeScript files to offer Stimulus-specific features: autocompletion for controllers/actions/targets, diagnostics for incorrect usage, code actions for quick fixes, and code navigation. Key capabilities include validating Stimulus controller existence, action correctness, and proper data attribute usage, with intelligent suggestions for corrections.
The Hyperledger Bevel Fabric Operator is a Kubernetes operator for managing the full lifecycle of Hyperledger Fabric networks. It provides custom resource definitions (CRDs) and controllers for Certificate Authorities (CAs), peers, ordering service nodes, chaincode (install, approve, commit), channels (main and follower), identities, network configurations, and an operator UI/API. The system also includes a kubectl plugin for CLI-based management. It supports multiple ingress controllers (Istio, Traefik, Gateway API), credential stores (Kubernetes Secrets, HashiCorp Vault), and database backends for the built-in Fabric CA. The operator vendors and patches upstream Hyperledger Fabric and Fabric CA libraries for cryptographic operations, MSP configuration, policy building, and channel configuration. The codebase is well-structured with generated client code, consistent controller patterns (finalizers, status conditions), and comprehensive integration tests. It is actively maintained under the Hyperledger Bevel project, with a large community and regular releases.