thehardwarestore.ai

git-log-tree is a single-file Bash CLI tool that renders a fancy, colored git log graph in the terminal. It wraps `git log` with `--topo-order`, `--parents`, and a custom pretty format, then parses the output to draw a tree using Unicode box-drawing characters and ANSI colors. The script handles complex branching, merges, and orphan commits, assigning colors to branches with an algorithm that minimizes reuse and ensures contrast. It respects the `NO_COLOR` environment variable and auto-detects color support. The tool pipes output through `less -F -R -S -X` for paging. The repository includes a comprehensive BATS test that creates a synthetic git history via fast-import and verifies the exact rendered output, along with a GitHub Actions workflow for coverage via kcov. The code is well-structured for a Bash script, using associative arrays and bit manipulation for efficient color sorting, but is monolithic with global state, limiting component reusability.

This repository is an open-source terminal-based AI coding assistant built in Rust, clean-room reimplementing Anthropic's Claude Code. It provides an interactive TUI (ratatui) for multi-provider LLM conversation (Anthropic, OpenAI, Google, and 30+ OpenAI-compatible) with a rich tool ecosystem for file editing, bash execution, MCP integration, code analysis, web fetching, and agent orchestration. The architecture is modular: a provider abstraction layer (`LlmProvider` trait), plugin system, slash commands, session management, and an Agent Client Protocol (ACP) for external IDE integration. The codebase is organized into 12+ workspace crates with clear separation of concerns, but many modules are still in active refactoring (issue #232) with stubs, TODOs, and incomplete feature gates (36 experimental features). The permission system, tool budget enforcement, and streaming decoders demonstrate strong engineering, while dual feature flag systems and global mutable state introduce maintenance risk. Overall, it is a feature-rich, well-architected application with some rough edges from ongoing migration.

nvfetcher is a Haskell-based CLI tool and library for automating Nix package updates. It integrates with nvchecker to monitor upstream version releases and uses the Shake build system to manage dependency tracking and incremental builds. The tool processes package definitions (from TOML config or Haskell DSL), fetches source code using appropriate methods (git, GitHub, URL, tarball, Docker), optionally extracts files, processes Rust Cargo.lock dependencies, and generates Nix expressions and JSON metadata for use in Nixpkgs. The architecture is modular with clear separation of concerns: configuration parsing, core logic, fetching mechanisms, version checking, extraction, and Nix expression generation.

This repository provides an xontrib (plugin) for the Xonsh shell that adds a `cheatsheet` command to open the project's README.md in a web browser. The README.md serves as a comprehensive cheat sheet for the Xonsh shell, covering installation, basics, and advanced topics. The repository also includes an example script demonstrating how to make web requests, process output, and use colored output in Xonsh.

MQTT-SN Tools is a suite of four command-line applications for working with the MQTT-SN (MQTT for Sensor Networks) protocol. The system provides mqtt-sn-pub for publishing messages, mqtt-sn-sub for subscribing to topics, mqtt-sn-dump for monitoring packets, and mqtt-sn-serial-bridge for serial-to-UDP bridging. All tools share a common C library (mqtt-sn.c/h) that implements the MQTT-SN protocol handling, including socket management, packet encoding/decoding, keep-alive mechanics, and topic mapping. The architecture is modular with clear separation between the protocol library and application-specific logic. Each tool follows a standard pattern: parse command-line arguments, establish UDP connection to an MQTT-SN broker, perform protocol operations (connect, publish/subscribe, etc.), handle incoming/outgoing packets, and clean up resources. The project has active maintenance with recent commits and a test suite.

Eslint Watch is a command-line tool that wraps ESLint to add file watching capabilities. It provides a CLI interface that forwards most options to ESLint while adding its own options like --watch, --changed, and --clear. The architecture is modular, with separate modules for option parsing, command handling, ESLint interaction, and file watching. The tool uses chokidar for file system events and keypress for keyboard input to trigger manual re-lints. It demonstrates solid engineering practices with a clear separation of concerns and a reusable option merging pattern.

Haaukins is a cybersecurity training and Capture The Flag (CTF) platform developed at Aalborg University. It orchestrates isolated lab environments for teams, combining Docker containers and VirtualBox VMs to deliver challenges. The system is built as a set of gRPC microservices: a central daemon manages event lifecycle, team assignments, and challenge verification; a store service provides persistence; and an exercise service defines challenge configurations. Participants access labs via a web frontend (Amigo) using browser-based RDP (Guacamole) or WireGuard VPN. The daemon also handles DNS/DHCP per lab subnet, real-time scoreboards via WebSocket, and keylogging for monitoring. The CLI client (hkn) allows administrators to manage events, teams, and exercises. The architecture is modular with clean interfaces for virtualization (Docker/VirtualBox) and storage (in-memory with hooks or gRPC backend), though some components show tight coupling and aging dependencies.

Telecrawl is a Go CLI application that imports Telegram Desktop's `tdata` session data and creates encrypted, versioned backups. It reads the local Telegram Desktop data directory (platform-specific paths for macOS/Linux), parses the tdata format, and stores chat archives in a SQLite-backed store with merge/restore/tombstone semantics. The CLI exposes commands for import, backup, restore, search, and media reference handling. It runs as a Docker image with a non-root user, read-only tdata mount, and persistent /data volume. Architecturally, it is a monolith with a `cmd/telecrawl` entry point delegating to `internal/cli`, which orchestrates importers (`tdata`, `postbox`) and the `internal/store` persistence layer. The store handles schema migrations, snapshot merging, and search. Backup uses a Git remote pattern with safety guards against path overlaps. The codebase includes CI workflows, release automation, and security checks. Maintenance is active with frequent dependency bumps and CI. However, the store package is large and mixes concerns, and tdata/postbox importers are format-specific and may break if Telegram changes its data format. Hardcoded platform paths and schema backfill migrations are drift risks. Despite some data-audit scripts and fixture data, the dominant character is a CLI application.

rTorrent is a high-performance BitTorrent client designed for headless (daemon) or ncurses-based terminal use. Its architecture is a monolithic event-driven application with clearly separated subsystems: core download management (libtorrent binding), display abstraction (ncurses windows and stubs), input handling, an extensive RPC layer supporting XMLRPC, JSONRPC, and SCGI, session persistence with async write-back, and a Lua scripting engine. The system exposes hundreds of commands for controlling torrents, trackers, peers, throttles, and DHT. Remote administration is a first-class feature, and the terminal UI is fully customizable via configuration. The codebase is mature and professionally structured, with strong test coverage and well-defined modular boundaries, though it carries some legacy dependencies (autotools, vendored TinyXML2, CppUnit) and deprecated command aliases.

go-chromecast is a Go application and library for discovering and controlling Google Cast (Chromecast) devices on a local network. It implements the CastV2 protocol using protobuf messages over TLS, with mDNS/DNS-SD discovery. The CLI, built with Cobra, exposes commands for status, playback, volume, text-to-speech, and a terminal UI; the same functionality is available programmatically through the application and cast packages.

cargo-sweep is a Cargo subcommand designed to selectively clean unused build artifacts from Rust project target directories. It operates based on various criteria such as file age, installed Rust toolchains, or target directory size limits, allowing users to reduce disk usage without performing a full 'cargo clean'. The tool is implemented as a standalone Rust binary that integrates with Cargo's metadata system to locate projects and analyze their build artifacts. The architecture centers around a modular design where command-line argument parsing (using clap) feeds into a criterion-based cleaning system. Key components include a sophisticated fingerprinting module that replicates Cargo's internal mechanism for associating build artifacts with specific Rust compiler versions, a timestamp handling system for time-based cleaning, and utility functions for human-readable byte formatting. The tool recursively discovers Cargo projects, evaluates which artifacts to retain based on the selected criterion, and safely removes the rest. Despite its technical sophistication, the project carries a maintenance warning in its README indicating it is currently unmaintained and lacks a dedicated maintainer. This is reflected in outdated dependencies (particularly cargo_metadata at version 0.9 versus the latest 0.18.0) and the project's reliance on the original author for issue triage and pull request reviews. While the code demonstrates strong engineering practices and reusable components, its future viability depends on renewed community stewardship.

ytsurf is a single-file Bash script that turns the terminal into a YouTube frontend. It scrapes YouTube search results and channel pages via curl and perl, parses the embedded JSON with jq, and presents results in a fuzzy-finder (fzf, rofi, sentaku, or tv) with thumbnail previews rendered via chafa. Once a video is selected, the script delegates playback to mpv (or iina/syncplay) and downloading to yt-dlp. The tool supports audio-only mode, format selection, subscription management with a personalized feed, watch history, playlists, and queueing. It caches search results and feed data to avoid redundant network calls, uses a config file for persistent settings, and offers multi-selector support. While functionally rich and well‑structured for a shell script, the codebase is tightly coupled into a single file (∼1400 lines), lacks unit tests beyond basic CI sanity checks, and relies on scraping fragile YouTube HTML. The packaging (Nix, Homebrew, AUR) and CI (ShellCheck on Linux/macOS) demonstrate good distribution and quality assurance.

Hermes Skins is a curated collection of YAML configuration files that define visual themes (skins) for the Hermes CLI agent. Each skin controls colors, spinner animations, branding text, ASCII art banners, and tool emojis. The repository includes a validation script (`validate_skins.py`) that enforces a strict schema (28 color keys, 4 spinner lists, 6 branding strings, and optional banner art) and checks for proper hex color format, required keys, and matching filenames. A screenshot generator (`generate_screenshots.py`) renders each skin's banner as ANSI text via Rich, converts it to HTML with ansi2html, and captures a PNG using Chromium via html2image. The skins themselves are the primary deliverable—they are consumed at runtime by the Hermes agent, which merges them with a default skin. The repository is well-organized with a clear contribution guide, PR template, and CI validation. It is not a standalone application but a configuration library with supporting tooling.

Minecraft Server Control Script (MSCS) is a monolithic Bash/Perl CLI tool for managing multiple Minecraft server instances on Linux. It provides a comprehensive set of actions: starting/stopping/restarting worlds, creating/deleting/enabling/disabling worlds, backing up (via rdiff-backup), mapping (via Minecraft Overviewer), updating server software, sending commands, and querying server status. The architecture is a single large shell script (msctl) with a wrapper (mscs) for system integration. Configuration is done via INI-style defaults files and per-world properties. The script relies on external tools: Java, Perl, Python, wget, rdiff-backup, rsync, socat, and flock. It integrates with systemd via provided service files and supports LSB init scripts. The codebase is functional and well-documented internally, but tightly coupled and monolithic, making extraction of individual components non-trivial.

Arx is a Haskell CLI tool and library that archives execution contexts (source code, command, environment) into a self-extracting POSIX shell script. The generated script sets up a temporary directory, unpacks archives, sets environment variables, and executes the command with trap-based cleanup. The system is designed for reliable, reproducible remote execution via SSH/sudo piped to sh. The Haskell library provides a clean type-class based interface (ARX, SHDAT, TMPX) for building such scripts, with sub-modules for shell variable validation, tar format detection, and a novel scheme for encoding arbitrary binary data into shell HEREDOCs with minimal overhead (handling NUL bytes and escape characters). The CLI uses a custom combinator parser built with Parsec. This is a well-architected, focused tool demonstrating deep knowledge of both Haskell and shell scripting.

Continue is an open-source AI coding agent that provides chat, autocomplete, edit, and agent capabilities across VS Code, JetBrains IDEs, and a standalone CLI. The architecture centers on a shared TypeScript core (`core/`) that handles LLM interactions, context providers, tool definitions, indexing, and configuration management. This core is consumed by three frontends: a VS Code extension (`extensions/vscode/`), a JetBrains plugin (`extensions/intellij/`), and a CLI (`extensions/cli/`) with a React-based TUI. A separate React GUI (`gui/`) runs as a webview in the IDE extensions. The system supports 50+ LLM providers through a plugin architecture in `core/llm/llms/` and uses a YAML-based configuration system (`packages/config-yaml/`) with a Hub for sharing assistants. Codebase indexing uses a content-addressed Merkle tree approach with a Rust sync library (`sync/`). The repository is now read-only and deprecated as of the final 2.0.0 release, with the team recommending users migrate to the CLI.

SmallCode is an open-source AI coding assistant CLI designed to run locally on consumer hardware with small language models (8B–35B parameters). It provides a full-screen terminal UI with streaming output, tool execution, and multi-turn agent loops. The system compensates for small-model limitations through a context budget engine, forgiving JSON parser, patch-first editing, early-stop detection, and TODO-driven planning. It supports multiple LLM providers (Ollama, LM Studio, llama.cpp, OpenAI, Anthropic, DeepSeek) with automatic escalation to stronger models on hard failure. The architecture is a monolith agent loop with modular subsystems: a plugin system for tools, commands, and hooks; a skill system for reusable prompt templates; a knowledge injection system for contextual notes; a memory store with SQLite/FTS5; a RAG index for code snippet retrieval; and an MCP client/server for tool interoperability. The codebase includes a compiled MarrowScript cognition layer with typed prompts, output validation, and budget tracking, though the dual implementation (hand-ported JS alongside MarrowScript sources) introduces drift risk. Key entry points include bin/smallcode.js (main CLI), src/tui/fullscreen.js (zero-dependency TUI), and src/compiled/cognition/ (prompts, routers, validation). The agent loop orchestrates user input, model calls, tool dispatch, and improvement loops. The repository also includes benchmark harnesses, trace recording, evaluation runners, and a provider wizard for configuration. Despite being marked as 'dead' in the README, the codebase exhibits high craftsmanship in several reusable components, though the large feature surface and experimental nature suggest maintenance challenges.

Apache Cordova CLI is a command-line tool for creating, building, deploying, and managing Apache Cordova-based mobile applications. It serves as a thin orchestration layer over the `cordova-lib` and `cordova-create` libraries, parsing user commands and delegating to those libraries for project management, platform/plugin operations, building, and running. The architecture is straightforward: a single entry point (`bin/cordova`) invokes `src/cli.js`, which uses `nopt` for argument parsing, then dispatches to appropriate functions (e.g., `create`, `platform`, `plugin`, `build`, `run`, `info`). The codebase is mature, well-tested, and actively maintained with CI, CodeQL, and license auditing. However, the CLI is tightly coupled to the Cordova ecosystem and offers no reusable components outside that context. The implementation is solid but follows standard patterns without exceptional craftsmanship.

Pipe Viewer is a Perl-based YouTube client providing both a CLI (`pipe-viewer`) and a GTK3 GUI (`gtk-pipe-viewer`). It allows users to search, stream, download, and manage YouTube content including videos, playlists, channels, comments, and captions. The core library `WWW::PipeViewer` abstracts YouTube data extraction via direct web scraping (ytInitialData, protobuf) and the Invidious API, with yt-dlp as a fallback for streaming URLs and comments. The architecture separates network resilience, caching, and format handling into reusable Perl modules (`DiskCache`, `Proto`, `ParseJSON`, etc.), though the CLI and GUI scripts are monolithic and tightly coupled to the library. External dependencies include `mpv`/`vlc` for playback, `yt-dlp` for advanced extraction, and `ffmpeg` for conversion. The project is actively maintained but operates on fragile, unofficial YouTube interfaces, making it susceptible to upstream changes.