Arcadia is a self-hosted, full-stack server management and automation platform. It provides a web-based dashboard (Vue.js frontend with Naive UI) and a CLI (shell scripts) for managing scheduled tasks (cron), daemon processes (PM2), file systems, environment variables, dependencies (npm, pip, apt, etc.), notification channels (17+ providers), alert rules, code synchronization (git/raw), and user authentication (JWT, TOTP 2FA). The backend is built with Node.js/Express, Prisma ORM (SQLite), and Socket.IO for real-time updates. A Telegram bot (Python/Telethon) and a message push SDK extend its reach. The architecture follows a modular pattern: the backend exposes REST APIs and OpenAPI endpoints with fine-grained permissions; the frontend is a compiled Vue 3 SPA with i18n support; the shell CLI provides a full-featured command-line interface for automation. Key subsystems include a cron engine with in-memory scheduling, a notification channel provider system with sliding-window throttling, an alert rule engine with regex matching and replace chains, and a dependency manager with serial queue operations. While the codebase demonstrates strong engineering practices—consistent validation patterns, reusable provider interfaces, and a well-defined config module—it also carries risks from committed minified frontend assets, shell script brittleness, and hardcoded paths. Overall, it is a capable and extensible platform for DevOps automation.
openupm-cli is a command-line interface for managing Unity Package Manager (UPM) dependencies. It allows users to add, remove, search, view, and list Unity packages from various registries (primarily OpenUPM and Unity's official registry). The tool modifies the Unity project's manifest.json file to add/remove dependencies and handles scoped registries for package resolution. It features a modular architecture with clear separation between CLI interface, application logic, domain models, and I/O operations. The codebase is written in TypeScript with comprehensive test coverage and follows semantic versioning for releases.
The repository implements LLaVA-VLA, a Vision-Language-Action model for robotic manipulation tasks. It extends the LLaVA framework to predict action sequences from visual inputs, proprioceptive state, and language instructions using a diffusion-based action head. The system includes training pipelines for fine-tuning on datasets like CALVIN, inference servers (Flask and Gradio) for real-time robot control, and evaluation tools for benchmarks. The architecture features modular vision encoders, projectors, and resamplers with factory patterns for flexibility, action tokenization for discrete action prediction, and integration with PEFT/DeepSpeed for efficient training.
This repository implements a Home Assistant custom integration that adds a visual, drag-and-drop card builder for Lovelace dashboards. Users can design custom dashboard cards by composing blocks (text, icons, gauges, charts, weather, etc.) in a canvas, configuring styles, entity bindings, and actions—all without writing YAML or code. The system includes a dedicated panel within Home Assistant, a custom Lovelace card renderer (`custom:card-builder-renderer-card`) for runtime display, and a marketplace for sharing cards via cardbuilder.pro. Architecturally, the project is split into a Python backend (`custom_components/card_builder/`) and a TypeScript/Lit frontend (`frontend/`). The backend handles integration setup, WebSocket APIs for CRUD on cards, presets, media, and account management. The frontend is a single-page application with panel views (dashboard, card list, editor), a designer canvas with Moveable-based manipulation, and a block system where each block declares its configuration, editor UI, and rendering logic. Key subsystems include a style resolver with preset inheritance and entity bindings (direct, map, threshold, condition, template), a drag-and-drop manager with adapters for canvas and containers, a chart data provider for history/statistics, and a document model with versioned migration. The codebase demonstrates high craftsmanship in its block abstraction, style system, and binding engine—patterns that could be extracted for other visual editors. However, some files are large and tightly coupled, with lingering FIXME comments and a few fragile DOM workarounds. The integration is actively maintained, with a clear roadmap and pro version planned, though the external marketplace dependency introduces some risk.
This is a Claude Code plugin that enables scheduling recurring and one-time tasks using native OS schedulers (launchd on macOS, crontab on Linux, Task Scheduler on Windows). Users describe tasks in natural language (e.g., 'every weekday at 9am review yesterday's code'), and the plugin converts that to cron expressions, registers the task with the OS scheduler, and executes `claude -p "prompt"` at the scheduled time. It supports autonomous execution with `--dangerously-skip-permissions`, git worktree isolation for tasks that modify code (creates a branch, runs Claude, commits and pushes changes), and provides commands to list, remove, run, and view logs of scheduled tasks. The architecture is modular: platform-specific scheduler implementations inherit from a base class, cron parsing and humanization are separate utilities, and execution history is stored as JSONL files. The codebase demonstrates strong security awareness with shell escaping, input validation via Zod schemas, and careful handling of user-provided values in generated shell scripts.
This repository provides the Bazel build rules and tooling for building Android applications (APKs, AABs, libraries) using Bazel. It includes Starlark rules for android_binary, android_library, android_local_test, etc., along with a suite of Go and Java tools for resource processing, dexing, R8 optimization, manifest merging, and mobile-install deployment. The codebase is production-grade, used internally at Google, and supports both WORKSPACE and Bzlmod. It features a well-architected processing pipeline pattern, a reusable flag system, and extensive test infrastructure. The repository is actively maintained with regular commits and CI, though it carries some technical debt from internal migration and legacy feature flags.
This repository provides reference implementations of common system design patterns in Python and Java. It is primarily an educational resource containing standalone algorithm implementations for consistent hashing, rate limiting (token bucket, leaky bucket, sliding window variants), and load balancing algorithms (round robin, weighted round robin, least connections, least response time, IP hash). The code serves as a learning tool for system design interviews and concepts rather than a production-ready application. Each implementation is self-contained with usage examples embedded in the source files. The repository has no external dependencies beyond standard libraries, making it easy to extract and study individual patterns.
Berty is a full-stack, privacy-focused, peer-to-peer messaging application. The system consists of a Go backend implementing the Wesh protocol (based on IPFS, libp2p, and OrbitDB) that provides core messaging, push notifications, authentication, replication, and directory services. The backend is exposed via gRPC and consumed by multiple clients: a React Native mobile app (with both a legacy JS variant and a newer Expo-based variant), a Go CLI with a terminal UI (mini) and a desktop GUI (Fyne), and native bridges for iOS and Android. The architecture is modular, with separate packages for error handling, authentication, push relay, and bot framework. Key entry points include the `berty daemon` CLI command, the mobile app entry points (`App.tsx` in both `js/packages` and `berty-bridge-expo/mobile`), and the bridge framework (`go/framework/bertybridge`). Data flows involve gRPC streams from the Go backend to the mobile clients, with event-driven state management and local encrypted storage via SQLCipher. External dependencies include libp2p, OrbitDB, gRPC, protobuf, and various platform-specific native modules for BLE, mDNS, and push notifications. The repository also contains auxiliary tools for infrastructure testing, rendezvous servers, and debugging (Tyber).
Sled is an embedded key-value store written in Rust that provides ACID transactions, crash safety, and high concurrency. It uses a lock-free architecture based on a lock-free pagecache, lock-free log, and lock-free B+ tree with epoch-based memory reclamation. The database supports multiple keyspaces, watch prefixes, merge operators, and a crash-safe monotonic ID generator. Currently in active development with a major rewrite underway (komora project), it is alpha software with known instability and frequent breaking changes, but demonstrates advanced concurrent data structure techniques.
This repository is a Hardhat-based template for developing Solidity smart contracts. It provides a pre-configured development environment with sensible defaults for compilation, testing, linting, and deployment. The core functionality is demonstrated through a simple `Lock` contract that implements a time-locked withdrawal mechanism, complete with custom errors, events, and comprehensive tests. The template integrates TypeChain for TypeScript bindings, Ethers.js for Ethereum interactions, and various tooling like Solhint, Prettier, and Solcover. It is not a production application but a starting point for new Solidity projects, emphasizing best practices and developer experience.
ILIAS is a large, modular, open-source Learning Management System (LMS) written primarily in PHP. In production, it provides a full-featured e-learning platform including course management, tests and assessments, surveys, forums, wikis, blogs, portfolios, SCORM content, certificates, chat, and social features. The architecture is a monolithic PHP web application with a component-based internal structure under `components/ILIAS/`. It uses dependency injection (DIC), ilCtrl for routing, a custom UI framework (ILIAS\UI) with factory and renderer patterns, GlobalScreen for top-level UI orchestration, and COPage for rich content editing. Entry points include `cli/setup.php` (installation), `cli/cron.php` (cron jobs), `login.php`, and various web service endpoints (SOAP, WebDAV, REST). External dependencies include MySQL, Node.js (for the chat server), and optional integrations like LDAP, Shibboleth, and LTI. The codebase shows active modernization with PHP 8.3/8.4, strict types, enums, and a structured setup/migration system, though it still carries legacy patterns (e.g., global `$DIC`, old GUI classes) that are being phased out via PHPStan rules and deprecation notices.
This repository implements the Cockpit Files module, a file manager web application embedded in the Cockpit server administration console. It provides directory browsing in list/grid views, breadcrumbs and GTK bookmarks, file upload/download with conflict handling, copy/paste, create/delete/rename/symlink operations, permission and ownership editing (including recursion and SELinux context display), and a modal text editor with change detection. The UI is a React 18/TypeScript SPA using PatternFly 6, packaged as a Cockpit manifest module with translations in 20+ languages. Architecture is a browser-side React application that talks to the Linux host exclusively through Cockpit's bridge APIs: directory listing via FsInfoClient, file operations via cockpit.spawn invoking standard CLI tools, streamed upload/download via fsreplace1/fsread1 channels, and a small embedded Python helper for reading SELinux xattrs. The custom esbuild build system bundles src into dist, injecting generated file-type mappings and PO translations at build time. There is no server-side application logic or data pipeline; the code is all presentation and client orchestration. Code quality is professional: components are separated by concern, dialogs use a coherent framework, and the integration test suite exercises major workflows in a real VM through Cockpit's testlib. However, the module is tightly coupled to Cockpit's internal React libraries and bridge protocol, and several HACK comments document workarounds for bridge limitations. Maintenance is active, with CI, Weblate translation sync, and packaging for RPM/Debian/Arch. Outside Cockpit, only the file-type lookup/plugin components are portable; the rest is module-specific.
datafusion-dft (dft) is a batteries-included Rust application that wraps Apache DataFusion into a multi-front-end SQL query and analysis tool. It provides four interfaces sharing one execution core: a scriptable CLI (file/command queries, benchmarking, FlightSQL client mode, CSV/JSON/Parquet/Vortex output), a ratatui terminal UI with SQL editor, paginated results, and history tabs, an Arrow FlightSQL gRPC server with full metadata and prepared-statement support, and an HTTP REST server. The core library (crates/datafusion-app) constructs a DataFusion SessionContext with a trait-based extension plugin system, dedicated CPU/IO executors, statistics collection, and observability hooks.
NaïveProxy is a censorship circumvention proxy that repurposes Chromium's network stack to mimic genuine Chrome HTTPS traffic at the TLS, HTTP/2, and QUIC protocol levels. The repository is a heavily trimmed Chromium source tree with custom patches for traffic padding, SOCKS5 client support, and a padding layer between proxy endpoints. It produces a statically linked `naive` binary (client and server) and an Android APK plugin (SagerNet). The architecture is a monolithic executable that bundles Chromium's networking libraries (BoringSSL, HTTP/2, QUIC) with a thin custom layer for configuration parsing and protocol padding. Key entry points are the `naive` binary (via command-line and config.json) and the Android plugin service. External dependencies include the Chromium source base (fetched at build time), BoringSSL, and system libs. The custom components (padding framer, config parser) are small, well-tested, and can be extracted for reuse in other proxy or traffic analysis projects.
GravitySnapHelper is a mature Android library that extends LinearSnapHelper to snap RecyclerView items to an edge (START, END, TOP, BOTTOM) or CENTER. It provides configurable fling distance limits, scroll speed, snap-to-padding support, and a snap listener. The library also includes GravitySnapRecyclerView, a drop-in RecyclerView subclass that wires up the snap helper with XML attributes, and OrientationAwareRecyclerView to resolve nested RecyclerView touch conflicts. The sample app demonstrates various configurations including horizontal and vertical snapping, decoration-aware snapping, and pager-like behavior. The code is clean, well-documented, and makes effective use of Android's RecyclerView API. It has a strong following (nearly 5000 stars) and receives active maintenance.
TiddlyWiki5 is a mature, extensible personal wiki application that runs entirely as a single HTML file in the browser or as a Node.js server. It manages content as individual 'tiddlers' — small, addressable pieces of text with metadata — and provides a powerful custom filter language for querying, transforming, and aggregating them. The application features a widget-based UI rendering engine, a pluggable wiki-text parser with dozens of rules, a built-in HTTP server with REST-like endpoints, encryption, and extensive integration plugins (geospatial maps via Leaflet/Turf, math typesetting via KaTeX, Markdown parsing, CodeMirror editing, QR codes, etc.). The architecture is highly modular: core functionality is implemented via module types (widgets, filter operators, parser rules, startup hooks, saver backends) that can be extended or overridden by plugins. The codebase has been continuously developed since 2011 and supports both client-side single-page application mode and server-side wiki mode. Despite its impressive extensibility and long history, the codebase shows signs of technical drift. The boot kernel (boot/boot.js) is a large monolithic file that mixes utility functions, the wiki store, module loading, and platform-specific startup logic. Many third-party libraries (e.g., JSZip v2.6.1, Leaflet.markercluster 1.5.3, minified CodeMirror modes) are vendored and outdated, requiring manual patching. The code style is inconsistent, with some modules using modern ES6+ features while others remain in ES5. The filter language and widget infrastructure are well-architected and reusable, but the tight coupling between core modules makes extraction for external use non-trivial. The project remains actively maintained with frequent commits, a large community, and an extensive test suite, making it a solid foundation for knowledge management applications, though significant refactoring would be needed to bring it to contemporary best practices.
Sonokai is a high-contrast Vim/Neovim colorscheme based on Monokai Pro, offering multiple variants (default, atlantis, andromeda, shusia, maia, espresso). It provides extensive customization options, support for tree-sitter, semantic highlighting, and optimizations for dozens of plugins. The repository includes a sophisticated code generation system that extracts syntax highlights from its own source and places them in after/syntax directories for on-demand loading, improving startup performance. It also comes with themes for popular statusline plugins (airline, lightline, lualine). The code is well-structured Vimscript with clear separation of concerns.
This repository contains a proof-of-concept exploit for two Linux kernel vulnerabilities (CVE-2026-43284 and CVE-2026-43500), collectively called 'Dirty Frag'. The exploit chains an xfrm-ESP page-cache write vulnerability (requires user namespace creation) with an RxRPC page-cache write vulnerability (does not require namespace creation) to achieve root privilege escalation on major Linux distributions. The single C source file (exp.c) implements both exploit paths and a fallback chain: it first attempts to overwrite /usr/bin/su with a minimal root-shell ELF using the ESP variant, and if that fails (e.g., due to AppArmor blocking user namespaces), it falls back to patching /etc/passwd's root entry to have an empty password field via the RxRPC variant, then spawns a root shell via su. The code demonstrates advanced kernel exploitation techniques including splice-based page cache injection, in-place crypto manipulation, and user-space porting of kernel crypto primitives (fcrypt). It is not a reusable library or framework but a targeted exploit PoC.
This repository is a large, actively maintained collection of ~1,000 standalone C++ solutions to LeetCode and similar interview algorithm problems, published by the 'codestorywithMIK' YouTube educator. It is organized into ~30 topic folders (Arrays, DP, Graph, Tree, Sliding Window, Segment Tree, Trie, strings, etc.) with per-topic READMEs, difficulty subfolders, and an extensive set of iPad PDF lecture notes accompanying YouTube videos. It is neither a deployable application nor a data/research project: it is a reference/educational code library whose primary consumption path is copying a solution into LeetCode's online judge or studying the annotated approaches. As such it is classified as 'application' only in the loose sense that it consists entirely of source code rather than data artifacts; in practice it is a non-executable solution bank, and this hybrid nature should be understood by anyone evaluating it for reuse.
Memospot is a desktop application that bundles the Memos note-taking service as a self-contained Tauri v2 wrapper. It manages the Memos server as a sidecar process, provides a SvelteKit frontend for settings and interaction, and handles configuration persistence, database migrations, window state, keyboard shortcuts, and auto-updates. The architecture is a Rust backend with a web frontend, using a Rust workspace with multiple crates for config, dialogs, sidecar management, port picking, and homedir resolution. The frontend is built with SvelteKit, Tailwind CSS, and uses Paraglide for i18n. The build system includes GitHub Actions CI/CD, Docker-based builds, and installers for Windows (NSIS/WiX), Linux (deb, AppImage, Flatpak), and macOS. The codebase demonstrates solid engineering practices with clean abstractions and reusable utility crates, though it has some pinned dependencies and complex CI workflows.