Mezzanine is a mature, full-featured content management system built on Django. It provides a hierarchical page tree with drag-and-drop ordering, a blogging engine with RSS/Atom feeds and importers from WordPress/Blogger/Tumblr, a dynamic form builder with CSV export, threaded comments with Akismet spam filtering, ratings, keywords/tags, user accounts with email verification and approval workflows, and inline editing via TinyMCE. The architecture is modular: core apps (pages, blog, forms, generic, accounts, twitter, galleries) are all Django reusable apps that integrate with the admin. Mezzanine's key innovation is a database-backed settings system where most configuration can be changed live through the admin interface, and a two-phase caching strategy that combines template fragment caching with a 'nevercache' tag for dynamic content. The codebase follows standard Django patterns (class-based views, managers, template tags, middleware) and is heavily internationalized (30+ languages). It is a production-grade CMS but shows its age in some vendored frontend libraries (jQuery 3.4.1, Bootstrap 3, TinyMCE 4.x) and contains deprecated modules (mobile, twitter).
Kaitai Struct is an umbrella project that provides a declarative language for describing binary data structures and a compiler to generate parser code in multiple target languages. The repository coordinates submodules for the compiler, runtimes for various languages (Java, Python, Ruby, etc.), format definitions, visualizer, tests, benchmarks, and documentation. Users describe a format in a .ksy file, compile it with the kaitai-struct-compiler to generate language-specific parser code, and use the corresponding runtime to parse binary data. The project includes CI workflows for building the compiler and publishing artifacts, and maintains a collection of ready-to-use format descriptions.
This repository provides a stealth browser automation MCP (Model Context Protocol) server that offers undetectable control over real browser instances (Chrome, Chromium, Edge) via the Chrome DevTools Protocol (CDP) and the `nodriver` library. It exposes 97 tools across 11 sections including navigation, DOM interaction, element extraction (styles, structure, events, animations), network interception and modification (including dynamic Python-powered hooks), CDP command execution, cookie management, tab control, and proxy forwarding with authentication. The architecture is a FastMCP-based server with singleton managers for browser instances, network interception, element cloning, and process cleanup. It supports stdio and HTTP transports, Docker deployment, and optional bearer auth. The system is designed to bypass anti-bot detection (Cloudflare, CreepJS, login walls) and is used for scraping, testing, and AI agent automation. While the codebase is well-structured and the functionality is comprehensive, there is some code duplication across multiple element cloner implementations and technical drift risk due to tight coupling with CDP APIs and the `py2js` transpiler dependency.
lewagon/data-setup is a Ruby-based documentation build system that generates the Le Wagon Data Science bootcamp environment setup guides for macOS, Windows, Linux, VM, and remote setups. It reads OS-specific YAML build specifications, resolves localized markdown partials from `_partials/` (including Spanish translations and remote partials fetched from other lewagon repositories), renders them with Liquid templating, and writes final bilingual guides back to markdown files. The primary entry point is `build.rb`, orchestrated by `lib/builder.rb` and `lib/generator.rb`, with CI via GitHub Actions rebuilding and committing generated files on every push. Despite the data-science branding, this is not a data-research repository: there is no pipeline, notebook, or model code. The only data-related artifacts are pinned Python package requirement files under `specs/releases/` and environment verification scripts in `checks/`. The dominant character is an application — specifically a content-generation toolchain for setup documentation. It demonstrates a clean partial-composition model, locale-aware fallback, remote content fetching with image-path rewriting, and parallel partial caching. The repository is actively maintained and technically current, though its reliance on pinned Python versions and remote GitHub raw URLs creates an ongoing need for upkeep. It is a well-structured niche tool rather than a general-purpose framework, but its modular design makes parts of the build pipeline reusable in similar multi-source documentation projects.
PhySO (Physical Symbolic Optimization) is a Python library for symbolic regression using deep reinforcement learning, with a strong emphasis on physics-informed constraints such as dimensional analysis. It discovers closed-form analytical expressions from data, supporting both single-dataset symbolic regression (SR) and multi-dataset class symbolic regression (Class SR) where the same functional form is shared across realizations with per-dataset free constants. The core architecture consists of a token-based program representation (reverse Polish notation), a custom LSTM-based policy network, a modular prior system (hard/soft length, physical units, nesting limits), and an efficient batch execution engine with optional parallel free-constant optimization. The library provides high-level entry points (`physo.SR()` and `physo.ClassSR()`), configuration presets, and a toolkit for expression manipulation and random generation. It includes extensive benchmarking infrastructure (Feynman and Class benchmarks), demos for real-world problems (e.g., Milky Way streams, US tariffs), and unit tests. External dependencies include PyTorch, NumPy, SymPy, pandas, scikit-learn, and matplotlib. While primarily a software library for symbolic regression, it is deeply research-oriented with benchmark result CSVs and analysis scripts, giving it a hybrid application/research character.
Photonix is a self-hosted, full-stack photo management application with AI-powered classification and search. The backend is a Django monolith exposing a GraphQL API, with background workers for importing, thumbnail generation, raw processing, and ML classification (color, objects, faces, location, style, events). The frontend is a React 19 single-page app built with TanStack Router, Apollo Client, Zustand state management, and a dark-themed shadcn/ui component library. The system supports multi-user libraries, invitations, map view, albums, and fine-grained search with facets. The architecture relies on a PostgreSQL database, Redis for task coordination and locks, and supervisor to manage numerous background processes. While the project shows solid engineering and a modern tech stack, it carries some technical debt from vendored ML models, TensorFlow 1.x compatibility, and hardcoded download URLs, and is explicitly not yet feature-complete.
This is a sample application from Microsoft demonstrating how to build a chatbot with Azure OpenAI and your own data using Retrieval-Augmented Generation (RAG). It is a full-stack web application with a Python Quart async backend and a React/TypeScript frontend. The backend handles conversation orchestration, integrates with Azure OpenAI for chat completions, and supports multiple data sources (Azure Cognitive Search, CosmosDB, Elasticsearch, Pinecone, etc.) for grounding responses. It also includes a comprehensive data preparation pipeline (scripts) for chunking documents, generating embeddings, and indexing into search services. The frontend provides a modern chat interface with features like streaming responses, citation display, chat history, and file upload. The repository is primarily an application but has a strong data engineering component, making it a hybrid. It is actively maintained, well-structured with tests and CI/CD, but has some technical drift due to preview APIs and outdated dependencies.
Szurubooru is an image board (booru) web application for uploading, tagging, and discussing media content. It features a client-side single-page application (SPA) built with vanilla JavaScript and a server-side Python backend using SQLAlchemy ORM with a RESTful API. The system uses PostgreSQL for data storage and is deployed via Docker containers. Key architectural concerns include a clean separation between client and server, with the client handling UI interactions and the server managing data persistence and business logic. The application implements common web application patterns such as event-driven client-side components, optimistic locking for concurrent updates, and a modular serialization framework for API responses. While the codebase demonstrates solid engineering practices, it shows signs of technical drift due to reliance on outdated base images (Node.js 14 and Python 3.9) and legacy build tools (browserify/babelify). The project is actively maintained, as evidenced by recent commits and ongoing issue activity.
This repository is the Python implementation of PowerView, a comprehensive Active Directory (AD) security assessment and exploitation tool. It provides a feature-rich CLI (with an interactive shell), a web-based UI (Flask + vanilla JS), and a Model Context Protocol (MCP) server for AI agent integration. The tool enumerates AD objects (users, groups, computers, GPOs, trusts, certificates, DNS, SMB shares, etc.), identifies security vulnerabilities (kerberoasting, AS-REP roasting, shadow credentials, ACL abuse, certificate template misconfigurations), and supports active exploitation (DACL modification, RBCD, coercion attacks, SMB file operations). It is designed for red team operations and AD security audits. The architecture is a monolith centered on a large `PowerView` class (in `powerview.py`) that orchestrates all commands and dispatches to specialized modules (e.g., `kerberoast.py`, `ca.py`, `exchange.py`, `ldapattack.py`). It supports both standard LDAP and a custom implementation of Microsoft's Active Directory Web Services (ADWS) protocol (SOAP over .NET Message Framing and NegotiateStream), enabling operations without conventional LDAP. The tool leverages Impacket for low-level Windows protocols (SMB, RPC, Kerberos) and includes a plugin system with decorator-based registration and before/after hooks. The web front-end offers interactive graph visualization, object exploration, and real-time command history, while the MCP server exposes AD operations to AI assistants. Key data flows involve LDAP/ADWS queries for object enumeration, SMB/RPC sessions for remote system interaction, and Kerberos tickets for authentication attacks. External dependencies include `ldap3` (forked), `impacket` (forked), `dsinternals`, `flask`, `werkzeug`, and client-side libraries (Cytoscape.js, Alpine.js, Tailwind CSS). The codebase is large and tightly coupled in places, but the custom ADWS implementation, plugin system, and vulnerability detection engine are notable achievements that could be extracted and reused.
A Python CLI tool for searching, downloading, and organizing doujinshi (self-published manga) from configurable mirror sites. The architecture uses a plugin system defined via abstract base classes (BaseParser, BaseModel, BaseSerializer, BasePlugin) and discovered through Python entry points, allowing support for multiple sites (e.g., nhentai) without modifying the core code. The core package handles CLI argument parsing, asynchronous image downloading via httpx/asyncio with retry and proxy support, export to CBZ/PDF/ZIP, generation of HTML viewers for local browsing, and SQLite-based download history tracking. The codebase is well-structured with clear separation between core utilities and plugin-specific logic, though it contains duplicated viewer template files that indicate incomplete cleanup.
HyperView is a CLI-driven toolkit for downloading TradingView market data, backtesting Python trading strategies with TradingView-parity fill assumptions, and optimizing parameters via Bayesian search (Optuna). The system is organized as a monolith with subcommands: download-data, backtest, hyperopt, pine-optimize, pine-batch-optimize, list-data, list-strategies. It features a pluggable strategy framework with auto-discovery, 20+ TA-Lib indicator wrappers, a backtester that simulates intrabar SL/TP paths, and a two-stage Pine input optimizer that exports optimized Pine scripts with injected best parameters. The codebase is well-structured with dataclasses, type hints, and a rich CLI output using the `rich` library. It includes unit tests for the Pine optimization pipeline and CLI parser. The repository is primarily an application, though it contains data engineering patterns in its downloader and caching layers.
This repository is a collection of competitive programming solutions and learning resources accumulated during interview preparation for a Microsoft SWE role. It contains implementations of algorithms and data structures from platforms like LeetCode, HackerRank, CodeChef, and others, organized by problem source and topic. The repository serves as both a personal record of solved problems and a reference for common coding interview patterns. The codebase consists of standalone solution files that implement specific algorithms to solve well-defined problems. Rather than a unified application, it's an educational repository where each file represents a self-contained solution to a particular coding challenge. The solutions demonstrate various techniques including two-pointer approaches, stack-based algorithms, in-place array modifications, and thread synchronization patterns. While the repository doesn't contain a single cohesive software system, it does include several reusable algorithmic patterns that could be extracted for use in other projects. Notable examples include the stack-based parentheses validation, two-pointer technique for sorted arrays, in-place array modification algorithms, and thread coordination mechanisms using Events and Semaphores. These components represent fundamental computer science concepts implemented with attention to correctness and efficiency.
Sopel is an IRC bot framework written in Python designed for extensibility through plugins. It provides core IRC protocol handling, plugin management, configuration systems, and utilities for time, calculation, and web interactions. The architecture centers around a plugin system where functionality is added via decorators (@command, @rule, etc.) and plugins can access bot state, configuration, and persistent storage. Key entry points include the `sopel` CLI for running the bot, `sopel-config` for configuration management, and `sopel-plugins` for plugin operations. The system supports IRCv3 features like SASL authentication and capability negotiation, uses SQLAlchemy for persistent storage of nick/channel data, and includes numerous built-in plugins for utilities such as calculations, URL title fetching, and user tracking. While actively maintained with recent commits, the codebase shows ongoing evolution with deprecated APIs marked for removal (e.g., sopel.loader, sopel.module) indicating moderate technical drift.
The Flask-DebugToolbar is a Flask extension that provides a debug toolbar with various panels for debugging purposes. It includes features such as syntax highlighting, line numbers, and bracket matching.
This repository is a pure Python library implementing elliptic curve cryptography algorithms, specifically ECDSA (Elliptic Curve Digital Signature Algorithm), ECDH (Elliptic Curve Diffie-Hellman), and EdDSA (Edwards-curve Digital Signature Algorithm). It provides key generation, signing, verification, and shared secret derivation functionalities across multiple curve types including NIST prime curves, Brainpool curves, and twisted Edwards curves (Ed25519/Ed448). The library is structured as a modular package with clear separation of concerns: high-level API in `keys.py`, low-level arithmetic in `ellipticcurve.py`, curve definitions in `curves.py`, ASN.1 DER handling in `der.py`, and utility functions for encoding/decoding in `util.py`. While the code is well-structured and includes comprehensive test suites, the project explicitly states it is not designed for production security due to vulnerability to side-channel attacks, recommending wrappers like `pyca/cryptography` for sensitive applications.
This is a Home Assistant custom component (integration) for controlling Gree-compatible air conditioners over the local network via UDP. It implements the Gree reverse-engineered protocol, supporting two encryption versions (AES-128 ECB and AES-128 GCM), device discovery, key negotiation, and full HVAC control (temperature, fan, swing, modes). The architecture follows Home Assistant's platform pattern: a climate entity as the core, with additional switch, sensor, number, and select entities for auxiliary features like X-Fan, lights, health mode, temperature step, and external temperature sensor selection. The integration communicates directly with the AC unit on UDP port 7000, encrypting commands with device-specific keys obtained during setup. It supports both UI config flow (with auto-discovery and cross-VLAN unicast scanning) and YAML configuration. The codebase is well-structured for a custom component, with clear separation of protocol logic (gree_protocol.py), temperature math (helpers.py), and entity definitions. Notable craftsmanship includes the TempOffsetResolver class for auto-detecting sensor offsets, the retry logic with progressive backoff and diagnostic failure classification, and the use of dataclass-based entity descriptions for switches and sensors. However, the main climate.py file is large (912 lines) and there are no automated tests, which is typical for community Home Assistant integrations.
Magic Areas is a Home Assistant custom integration that turns HA's area registry into an occupancy-aware automation layer. In production it listens to entity states across configured areas, computes presence from motion sensors, device trackers, and occupancy binary sensors, manages clear timers and secondary states (dark, sleep, extended), and publishes derived entities: area presence binary sensors, smart light/fan/cover/media groups, aggregate sensors, and feature-override switches. It is event-driven and tightly coupled to Home Assistant internals: the area/entity registries, dispatcher, event bus, async timers, and group entities.
BatMON is a Home Assistant add-on and standalone Docker application for monitoring battery management systems (BMS) over Bluetooth Low Energy (BLE) and serial connections. It decodes telemetry from ~25 BMS families (Daly, JK, ANT, Renogy, Seplos, etc.) and publishes normalized data to MQTT for Home Assistant, or directly to InfluxDB. The architecture is a Python asyncio application with a BMS abstraction layer (`bmslib`) that defines a common interface (`fetch()`, `fetch_voltages()`) and model-specific decoders. The main entry point is `main.py`, which dispatches to HA add-on or standalone mode via `entrypoint.sh`/`addon_main.sh`. Data flows from BMS hardware through BLE/serial adapters into decoder classes, then to MQTT/InfluxDB via a GUI wire format (`bmslib/wire/model.py`). External dependencies include bleak (BLE), paho-mqtt, influxdb, and Home Assistant add-on infrastructure (bashio, supervisor). The project includes a Helm chart, Docker multi-arch builds, and a test suite with known-answer vectors for CRC/AES and protocol decoders.
Milo is a self-hosted Discord bot designed for community operations, support, and lightweight moderation. It features a modular architecture using discord.py cogs to separate concerns like AI chat, economy, farming, games, moderation, and utility functions. The bot uses SQLite for persistent storage of per-guild data (economy balances, farming progress, reminders) and includes mechanisms to prevent race conditions in economy operations via per-guild locking. Configuration is managed through environment variables and a local config.json file, with support for guild-specific overrides for features like AI chat API keys. The bot includes AI-assisted chat with optional web search, a per-guild economy with jobs and gambling, a farming progression system, mini-games (Tic-Tac-Toe, guess the number), social interaction commands (hug, slap), media fetching (memes, cat/dog pictures), and moderation tools (warnings, automod for invites/links/bad words). Utility commands cover reminders (with recurring and snooze options), AFK status, server information, and more. Milo emphasizes privacy and control for community owners, with all data stored locally and no required external services beyond Discord for core functionality.
This repository provides a GNOME Nautilus (Files) extension that allows users to define custom context menu actions, replacing the defunct 'filemanager-actions' project. The extension is implemented in Python using nautilus-python and GObject introspection, supporting two modes of command interpolation (v1 legacy and v2 improved), shell and native tokenization, and extensive filtering based on file type, mimetype, path patterns, permissions, and custom conditions. A graphical configurator is provided as a local web application served by a Python HTTP server, featuring a JSON Schema-driven UI built on a forked json-editor with Ace code editor integration, running entirely locally with no external network calls. Architecturally, the system consists of two main components: the Nautilus extension (Python) and the configurator (Python HTTP server + HTML/JS frontend). The extension hooks into Nautilus via the MenuProvider interface, loads configuration from a JSON file, builds menu items recursively with filtering, and executes commands via subprocess. The configurator is a standalone HTTP server that serves the UI, reads/writes the config file, and can restart Nautilus. Communication between the two is file-based (config.json), with the extension polling for changes every 30 seconds. Key reusable components include a tokenizer for shell and native command lines with context-aware escaping, a placeholder expansion engine with singular/plural support, a config loading and normalization pipeline with validation, and a UI model transformation pattern for schema-driven interfaces. The code is well-structured but lacks automated tests and relies on vendored third-party JavaScript libraries.