★ 1,671RustMPL-2.0
httm is a CLI for finding and restoring file versions from ZFS/btrfs/nilfs2 snapshots, Time Machine, or Restic backups, with both interactive and scriptable modes. Targets Linux/BSD/macOS sysadmins and power users who already snapshot their filesystems but hate digging through .zfs/snapshot directories by hand.
httm's real trick is deduplicating file versions by mtime and size, so instead of scrolling through twenty identical copies in .zfs/snapshot you get the ones that actually differ. It does this across ZFS, btrfs snapper, nilfs2, Time Machine, and Restic through one CLI, which is unusual — most snapshot browsers lock you into one backend.
The roll-forward model (instead of destructive rollback) and recursive deleted-file discovery are the kind of features you only appreciate the day you need them. The companion scripts (ounce, bowie, nicotine) are a good tour of what's possible once you treat snapshots as a queryable history rather than a backup you hope you never touch.
What to know going in: it shells out to zfs/btrfs CLIs and parses their output, which is inherently fragile across distro versions — the README itself flags open FreeBSD and glibc/musl issues. Restore operations touch live files and snapshot guarding is opt-in, not default, so read the docs before you run anything with a flag you don't recognize. It's also a single-maintainer project, and some companion scripts want snapshot privileges granted up front.
Our full take →GitHub ↗
★ 821PythonNOASSERTION
asammdf is a Python library (with C extensions and an optional Qt GUI) for reading and editing ASAM MDF/MF4 measurement files, the format used in automotive and industrial data logging. It's aimed at engineers working with CAN/LIN bus logs and sensor telemetry who need to parse, filter, convert or export large measurement files.
If you've ever had to touch an MF4 file from a CAN bus logger, you know how little good open-source tooling exists for it. asammdf actually gets into the weeds — CDBLOCK maps, channel arrays, zipped data blocks, attachments — and backs it with C extensions and lz4/isal so it doesn't fall over on large files. The export paths to pandas, HDF5, Matlab, CSV, and parquet cover what people actually do with this data, and the Signal class handles multi-rate channel alignment, which is the actual headache in this domain.
The project also takes maintenance seriously: mypy strict, ruff, CI across Python 3.10 through 3.14, and a benchmarks folder tracking regressions instead of just vibes.
What to know going in: the README is upfront about gaps — sample reduction blocks are ignored, event block support is incomplete, channel hierarchy isn't handled, and bus logging beyond CAN/LIN isn't there. If you need full MDF4 spec fidelity you'll hit walls. Bus logging also pulls in canmatrix plus external DBC/ARXML files, which is an extra dependency chain to manage. The GUI is a large PySide6 codebase bundled into the same repo, worth knowing if you only want the parser. It's also effectively a single-maintainer project, which matters more than usual given it's used in automotive-adjacent tooling.
Our full take →GitHub ↗
★ 773RustMIT
purple is a terminal-based SSH config manager and TUI in Rust that syncs ~/.ssh/config with 18 cloud providers, monitors live tunnels, and manages Docker/Podman containers across a fleet over plain SSH. Aimed at people managing a large or dynamic set of SSH hosts who are tired of hand-editing their config after every Terraform apply.
The hard part of a tool like this is editing ~/.ssh/config without wrecking it, and purple does that part properly — in-place parsing and writing that preserves comments, includes, and directives it doesn't recognize. That's the detail that separates a tool you'll trust from one you'll avoid. Container and tunnel management riding over existing SSH connections (rather than a separate agent or open ports) is also the right security tradeoff for a tool with this much reach into your infrastructure.
Provider coverage is wide — AWS, GCP, Azure, Hetzner, Proxmox, Vault SSH certs — and there's real test depth behind it, including a fuzz target on the config parser.
What to know going in: this is a lot of surface area for one maintainer to keep correct — 18 providers, Vault integration, an MCP server, container management, tunnels. The MCP server in particular means AI agents can touch your SSH config and credentials, which is worth scrutinizing yourself rather than taking the README's audit claims at face value. No Windows support, and as a young, fast-moving single binary, don't bet production infra on its config-sync behavior staying stable release to release.
Our full take →GitHub ↗
That's the list this week. If you want these picks in your inbox instead of hunting them down yourself, the email signup is on the homepage — one email, no noise.