Omarchy is a comprehensive, opinionated Linux desktop distribution built on Arch Linux with Hyprland as the tiling window manager and a custom Quickshell-based (Qt QML) desktop shell. It provides a polished, keyboard-driven user experience with extensive theming, a plugin system for shell widgets/panels/services, system management CLI tools (updates, migrations, hardware detection, package management), AI agent integration, clipboard manager, notifications, OSD, and more. The architecture is monolithic around a long-lived QML process, with shell scripts handling system-level operations. The repo includes a full installer, migration scripts, default configurations, and a manual. It is actively maintained with a large test suite and demonstrates strong engineering practices in its QML component library, IPC patterns, and guard evaluation system. While not a research project, it contains utility scripts for audio tuning and disk/network speed tests.
Nixpkgs is the largest, most comprehensive package repository for the Nix package manager and the NixOS Linux distribution. It contains over 140,000 package definitions spanning virtually every domain of software, along with the build infrastructure, standard environment, and NixOS system modules needed to build and configure a complete operating system declaratively. The repository is not a single application but a collection of Nix expressions, shell scripts, Python tools, and Rust utilities that together form a reproducible, source-based distribution framework. It provides a modular module system for declarative configuration, a generic build phase hook mechanism, extensive CI automation for PR review and package updates, and a sophisticated test driver for integration testing. The codebase is actively maintained with thousands of contributors, and its architecture emphasizes composability, reproducibility, and cross-platform support.
Secureblue is a security-hardened Linux distribution project built on Fedora Atomic (Silverblue, Kinoite, Sericea, Cosmic, IoT, and SecureCore variants). It produces bootable OCI container images via BlueBuild recipes and GitHub Actions CI, applying extensive hardening: kernel module blacklists, hardened kernel arguments, sysctl tuning, SELinux policy enforcement, systemd service lockdowns, setuid removal, secure boot with UKI signing, and DNS hardening. The runtime includes a comprehensive audit tool (audit_secureblue.py) that verifies security posture across ~30 categories with i18n support, plus interactive ujust commands for toggling hardening features.
OpenHPC is a community-driven software distribution and infrastructure framework for High Performance Computing (HPC) clusters. It provides a collection of RPM packages, installation recipes, and testing infrastructure to deploy and manage HPC environments on Linux distributions such as RHEL, SUSE, and openEuler. The repository serves as the build system and validation suite for the distribution, ensuring compatibility across multiple MPI implementations, compilers, and scientific libraries. It does not function as a single application but rather as a meta-package and deployment framework for HPC systems.
This repository is the build system for AvyOS, a Linux distribution that compiles all packages from source using a custom Go-based tool called 'ignite'. The system defines hundreds of YAML recipes under `elements/` for building the kernel, system libraries, desktop environments (KDE, GNOME, Xfce, Sway, etc.), development toolchains, and applications. The ignite tool handles dependency resolution, source fetching, containerized builds (via bubblewrap), and image generation (ISO, disk images, OSTree commits). The architecture is a declarative recipe system with reusable includes, patch management, and a web dashboard for monitoring builds. Key entry points are the `ignite` CLI and the YAML recipe files. External dependencies include upstream source tarballs, patches, and a custom build environment. The repository also includes configuration for secure boot, A/B updates, and live ISO booting. While the codebase is well-structured and demonstrates significant engineering effort, it is a personal project with limited documentation, many TODO comments, and potential drift due to custom kernel versioning and future-dated Go version requirements.
This repository is a comprehensive build system and distribution for Armbian, a lightweight Linux distribution for ARM devices, specifically targeting Amlogic, Rockchip, and Allwinner SoCs used in TV boxes and single-board computers. It provides scripts and GitHub Actions workflows to build custom Armbian images, compile kernels, and manage system software. The architecture is based on a layered filesystem overlay pattern: common-files (shared across all devices), platform-files (per-SoC family), and different-files (per-board overrides), allowing flexible device-specific customization. Key entry points include the `rebuild` script for local image building, GitHub Actions workflows for CI, and a suite of `armbian-*` command-line tools for end-user system management (install, update, kernel management, software center). The project includes a software center with dozens of pre-configured Docker, desktop, and service applications, and extensive device support documented in a model database and per-board boot configurations. While the codebase is functional and widely used, it exhibits high duplication across board-specific files, contains binary device tree blobs without accompanying source, and has several hardcoded paths and vendor-specific dependencies that increase maintenance burden.
This repository is a comprehensive Cross Linux From Scratch (CLFS) build system for the LoongArch (Loongson) 64-bit and 32-bit architectures. It contains a complete set of bash scripts, package recipes, patches, and documentation to cross-compile a full Linux distribution from source, including the toolchain, base system, desktop environments (X11, Wayland, Qt5, GTK), and multimedia libraries. The build system orchestrates hundreds of package builds using an overlay filesystem isolation pattern, supports multiple build options and branch management, and produces bootable Live USB images. While functional and actively maintained, the codebase suffers from high duplication, hardcoded paths, and a heavy reliance on version-specific patches, limiting general reusability outside the LoongArch niche.