TiDB is a production-grade, open-source distributed SQL database with MySQL compatibility, horizontal scalability, strong consistency (ACID), and HTAP capabilities via TiKV (row store) and TiFlash (columnar store). The architecture separates compute (TiDB Server) from storage (TiKV/TiFlash) with PD for cluster management. Key entry points: cmd/tidb-server (SQL layer), lightning/cmd/tidb-lightning (TB-scale import), br/cmd/br (backup/restore), dumpling/cmd/dumpling (export). The codebase demonstrates exceptional craftsmanship with a modular design: the parser (pkg/parser) is a standalone MySQL-compatible SQL parser used by external projects; pkg/objstore provides a unified storage abstraction (S3/GCS/Azure/local/HDFS) with compression/encryption; pkg/dxf/framework implements a distributed execution framework with scheduler/task-executor/planner; pkg/timer provides distributed cron/interval scheduling with persistence; pkg/extension enables plugin-based authentication/session-hooks/custom-functions; pkg/util/chunk/arena/zeropool/mvmap/intset/bitmap provide high-performance columnar processing and memory management; pkg/expression uses code generation for vectorized SIMD evaluation; pkg/planner implements a Cascades-based cost-based optimizer with plan caching; pkg/ddl executes online schema changes via job-based distributed backfill with schema versioning; pkg/statistics maintains histograms/CMS/FM-sketch with auto-analyze priority queues. The repo includes comprehensive testing (unit, integration, realtikv, chaos) and modern Go practices (generics, interfaces, DI).
Ghidra is a software reverse engineering (SRE) framework developed by the NSA. It provides a full-featured desktop application for analyzing compiled binaries, supporting disassembly, decompilation, debugging, and scripting across multiple architectures (x86, ARM, MIPS, PowerPC, RISC-V, etc.). The system is modular, built on a plugin architecture with services, actions, and extension points discovered at runtime. Key entry points include the GUI launcher (ghidra.Ghidra) and headless mode (ghidra.GhidraRun), as well as a Gradle build system for extension development. The debugger integrates with GDB, LLDB, dbgeng, drgn, and x64dbg via a Trace RMI protocol, and includes a p-code emulator and JIT compiler. Ghidra also offers binary similarity search (BSim), version tracking, and a rich API for scripting in Java, Python, and Jython. External dependencies include Java 17, Gradle, and optional third-party tools for PDB and DWARF processing.
Django Control Room is a plugin framework for building Django admin tools, called 'panels'. It provides a centralized dashboard that automatically discovers installed panels via Python entry points, renders them with a shared design system, and integrates them into the Django admin sidebar. The hub also exposes a Model Context Protocol (MCP) endpoint that aggregates all panel tools for AI agent integration. Panels are independent packages built on the companion `dj-control-room-base` library. The codebase demonstrates strong architecture: a collision-proof registry key derived from PyPI distribution names, featured panel verification to prevent squatting, dynamic admin proxy model registration, and a production-ready MCP transport implementing the Streamable HTTP specification. It includes comprehensive tests covering registry behaviour, admin integration, MCP endpoints, and utility functions.
Oh My Zsh is a community-driven framework for managing Zsh shell configuration. It consists of a core library (lib/), over 200 plugins providing aliases, functions, and completions for development tools and workflows, and over 100 prompt themes. The system is loaded by sourcing oh-my-zsh.sh, which initializes libraries, plugins, custom configurations, and the chosen theme. Plugins follow a consistent structure and many generate completions asynchronously. The repository also includes install/update/uninstall tooling and CI automation for dependency updates. While the vast majority of files are simple aliases or READMEs, several components exhibit high craftsmanship—notably the emoji definitions (auto-generated from Unicode data), the git prompt library (lib/git.zsh) with async support and security patches, the Zsh Navigation Tools (plugins/zsh-navigation-tools) providing full-screen interactive widgets, and the dependency updater script. Some content is stale (outdated completions for rustc, scala, yarn v1, docker-compose v1) and there is a long tail of low-effort plugins, but the core framework is well-maintained and actively developed.
OWTF (Offensive Web Testing Framework) is a full-stack web application for automated and manual penetration testing. The Python/Tornado backend exposes a JWT-protected REST API for managing targets, sessions, plugin worklists, workers, reports, and proxy history, while the React/Redux frontend provides dashboards, data tables, plugin marketplace, and proxy controls. The application also includes a customizable intercepting HTTP/HTTPS proxy with SSL certificate generation, an interceptor chain for header/body/URL/delay modification, transaction history, a repeater, and live interception - comparable in scope to a Burp Suite-style tool. Execution is plugin-driven: built-in Python plugins covering web, network, and auxiliary tests, plus wrappers around external tools like Nikto and Arachni, are run by multiprocessing workers. Community plugins can be uploaded after AST-based static validation that blocks dangerous imports and execution patterns. The system stores plugin outputs, deduplicates them via SHA-256 fingerprints, tracks execution metrics, and supports HTML reporting. User authentication includes JWT, email verification, OTP, and admin role management. Architecturally, this is a monolith with modular managers and a REST API, not microservices. Deployment targets Docker Compose, Kubernetes, and cloud Terraform. The codebase contains genuinely reusable components: AST-based plugin validation, cross-platform file locking, output fingerprint deduplication, structured logging, and SQLAlchemy query helpers. However, it also carries significant legacy debt: old frontend patterns (React 16 class components, Redux 3, Redux-Saga 0.16), Python 2 remnants in scripts, hardcoded secrets in compose files, and several stub or placeholder external plugins. The repository is fundamentally an application rather than a data research project; bundled dictionaries and execution metrics serve the security workflow but do not define its primary character.
This repository contains `plugin.video.youtube`, a Kodi Media Center add-on that provides full YouTube browsing, search, subscription management, and video playback with adaptive streaming (MPEG-DASH, HLS), subtitles, and multi-user OAuth authentication. Architecturally, it is a Kodi plugin with a background service, an embedded HTTP server for streaming proxy and API configuration, and a layered framework (Kodion) offering abstract base classes for context, items, settings, caching, and network requests. The codebase is substantial (262 files) and demonstrates solid engineering with reusable patterns such as a generic SQLite key-value store (`Storage`), a robust HTTP client with retry/caching hooks, centralized logging with sensitive data redaction, and an item model hierarchy convertible to Kodi ListItems. However, several components depend on reverse-engineered YouTube InnerTube endpoints and JavaScript signature extraction (`cipher.py`, `ratebypass.py`), which are fragile and known to be partially broken (signatureCipher and nsig handling are disabled). The add-on also maintains Python 2/3 compatibility shims and version-dependent Kodi workarounds. Localization is extensive but many translations are incomplete. Overall, the add-on is actively maintained and functionally comprehensive, but its heavy reliance on brittle reverse-engineering and the accumulation of legacy compatibility code introduce moderate technical drift.
OpenMod is a .NET-based plugin framework designed for extensibility across game servers and applications. It provides core services including dependency injection, event handling, command processing, permission systems, user management, and configuration management. The framework features a modular architecture with platform-specific adapters for games like Unturned and Rust, enabling developers to create plugins that extend functionality without modifying the core. The system uses an event-driven approach for loose coupling and supports self-updating via NuGet package management. While primarily focused on game server modding, the core abstractions are general enough to apply to other extensible application scenarios.
FISSURE is a modular RF signal-intelligence and reverse-engineering framework. In production it provides a PyQt5 dashboard for spectrum survey, IQ capture/playback, burst conditioning, signal classification, protocol discovery, targeted transmission, and fuzzing across SDR hardware such as USRP, HackRF, LimeSDR, RTL-SDR, PlutoSDR, and bladeRF. It coordinates distributed sensor nodes through a HIPRFISR hub over ZMQ, integrates with TAK via Cursor-on-Target messaging, and supports plugin-based automation operations. The repository also contains a very large GNU Radio flow graph library (maintained for GR 3.8 and 3.10), custom OOT blocks for ADS-B, Bluetooth, ACARS, X10, Z-Wave, fuzzing, and wideband detection, plus packet-crafting and replay tooling for security research.
This repository is a heavily modified fork of the RuneLite client for Old School RuneScape (OSRS), extended with a comprehensive automation and botting framework branded as 'Microbot'. The system provides a full game client with a plugin architecture, overlays, configuration system, and event bus, plus a large set of automation scripts for questing, combat, walking, banking, and inventory management. The core application is a Java desktop client using Swing, Guice dependency injection, and LWJGL for GPU rendering. Key entry points include the RuneLite main class, the Microbot plugin (which orchestrates script execution), and an HTTP agent server that exposes client state and allows remote control. The architecture is modular with composite Gradle builds for the cache, API, and client modules, but the microbot automation code is tightly coupled to game internals and relies on hardcoded IDs and reflection, making it fragile to game updates. The codebase integrates a vendored shortest-path planner (upstreamPlanner) for pathfinding, a quest helper subsystem with hundreds of quest-specific step classes, and a natural mouse movement library for human-like input simulation. External dependencies include OkHttp for network requests, Gson for serialization, and FlatLaf for UI theming. The project also includes cache-reading tools for extracting game definitions (items, NPCs, objects, interfaces, scripts) and a crowdsourcing plugin for collecting gameplay data. While the official RuneLite plugins are preserved, the majority of development effort appears focused on the automation layer, which introduces significant maintenance risk and potential policy violations.