thehardwarestore.ai

Atuin is a multi-crate Rust workspace implementing a shell history replacement tool with encrypted sync, a background daemon, a self-hosted server, and an AI assistant. The system replaces the default shell history with a SQLite database that records additional context (exit codes, working directories, session IDs, command durations) and provides fast, fuzzy search via a TUI. History is captured through shell hooks (bash, zsh, fish, nushell, xonsh, PowerShell) and optionally via a PTY proxy that captures command output for full-text search. A background daemon (atuin-daemon) manages history journaling, output capture persistence (Fjall blob store + SQLite FTS5 index), AI session capture from coding agents (Claude Code, Codex, opencode, Pi), and encrypted record sync with the server. The server (atuin-server) is an Axum HTTP application supporting SQLite, Postgres, and MySQL backends, providing user authentication, record sync endpoints, and capability negotiation. The AI subsystem (atuin-ai) includes a TUI chat interface, inline command mode, MCP server, skills system, and permissions framework for safe tool execution. Key entry points include the CLI binary (crates/atuin/src/main.rs), daemon boot (crates/atuin-daemon/src/daemon.rs), server launch (crates/atuin-server/src/bin/main.rs), and AI inline command (crates/atuin-ai/src/commands/inline.rs). External dependencies include SQLite, tokio, tonic (gRPC), Axum, serde, paseto, and various shell-specific integrations.

This monorepo provides a suite of libraries and CLI tools for generating changelogs from git metadata according to the Conventional Commits specification. The core pipeline consists of: a git client to fetch commits, a parser to extract structured data from commit messages, a filter to remove reverted commits, and a writer to render the changelog in Markdown. Additional packages handle version bump recommendations, preset loading (Angular, Conventional Commits), and template rendering. The system is designed for both programmatic use via builder-style APIs (e.g., `ConventionalChangelog`, `Bumper`) and direct CLI invocation. It supports multiple git hosting platforms (GitHub, GitLab, Bitbucket) and is configured through presets that define commit type effects, reference formatting, and section ordering. The architecture is a monorepo with 11+ independently published packages, each with its own tests, TypeScript definitions, and CLI entry points. The codebase is actively maintained, with frequent releases, breaking changes managed through major version bumps, and a migration from Handlebars to render functions. It requires Node.js >= 22 and is fully ESM. The project also includes a documentation website (Astro/Starlight), CI/CD via GitHub Actions, and an AI agent skill for commit message guidance. While primarily a developer tool, the repository demonstrates strong software engineering practices: clean separation of concerns, stream-based processing for large commit histories, a preset plugin pattern, and comprehensive test coverage including real git repository interactions. The lower-level packages (parser, filter, writer, git client) are designed to be reusable in other contexts, and the template utilities provide a foundation for custom changelog formatting.

Star History is a web application that visualizes GitHub repository star growth over time through interactive charts and embeddable SVG badges. The system consists of a Next.js 14 frontend with D3-based chart rendering, a Hono backend that generates SVG charts and Open Graph cards on demand, and a shared code library used by both. A data pipeline (gh/) fetches repository metadata from the GitHub API and weekly activity stats from BigQuery (GitHub Archive), stores them in SQLite, and exports JSON files consumed by the frontend for leaderboards, weekly rankings, and star count pyramids. The application also includes a blog with curated open-source project roundups, a sponsor system, and a Chrome extension for quick chart viewing. Architecturally, the frontend uses URL hash-based state management to persist chart configurations (repos, timeline mode, log scale) and supports embedding via iframe or SVG. The backend caches star data, SVG charts, and OG cards using LRU caches with TTL and size limits, and rotates GitHub API tokens with cooldown to handle rate limits. The shared chart utilities (axis drawing, labels, legend, watermark) are used both server-side (via JSDOM) and client-side, demonstrating a clean separation of rendering logic. External dependencies include the GitHub REST API, BigQuery for weekly stats, GH Archive for event data, D3.js for chart rendering, JSDOM and Satori for server-side SVG/OG card generation, and SVGO for SVG optimization. The project is deployed with Docker containers (frontend on Cloudflare Pages, backend on GKE) and uses GitHub Actions for weekly data refreshes and deployments. While primarily an application, the repo has a strong data pipeline component that ingests, transforms, and exports structured data about GitHub repositories. This hybrid nature is evident in the gh/ directory, which functions as an ETL pipeline, and the blog content that analyzes open-source trends using star history data.