Open-source project
cashapp/hermit avatar
cashapp/hermit

Hermit: Project-Local Toolchains That Bootstrap Themselves

🐚 Hermit manages isolated, self-bootstrapping sets of tools in software projects.

953 stars122 forksGoApache-2.0

At a glance

What is it?
Hermit from Cash App gives each project its own isolated, self-bootstrapping set of tools for Linux and Mac. It trades global installs for per-repository consistency, but the model has real costs in storage and onboarding.
Who is it for?
Adopt Hermit if your team or CI regularly fights over tool versions and you want a single, checked-in source of truth for every project's binaries. Skip it if you work on small, short-lived repos where the per-project download and disk overhead outweigh the consistency gain.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 3 days ago.
What is it written in?
Mainly Go, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • cashapp/hermit953 ★ · +42
Star history
Repository2026-08-232026-11-15
cashapp/hermit911953

42 Stars in the last 84 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The Problem: Tool Drift Across Teams and CI

The core mechanism is the self-bootstrapping set. A Hermit-managed project contains a directory that holds the tool manifests and the actual binaries. When a developer enters the project or runs a command, Hermit activates the environment, rewriting PATH so that the project's tools take precedence. The tools are installed on demand, and the environment is isolated from the global system tools. The README does not go into the internals, but the repository layout and the description imply a manifest-driven approach: each tool has a definition, and Hermit resolves and fetches the correct version. Because the set is self-bootstrapping, a new contributor or a fresh CI checkout can get the full toolchain without a pre-existing installation step. The bootstrap process is what distinguishes Hermit from a simple version manager like nvm or pyenv, which require a global install first.

What Runs Where: Linux and Mac Only

The repository is written in Go, which is a sensible choice for a tool that needs to be fast, statically compiled, and easy to distribute. The binary must run on both Linux and macOS, and Go's cross-compilation makes that straightforward. The release history shows active maintenance, with three releases in the span of a few months in 2026. The project is not archived, and the last push is recent. That is a positive signal for adoption, though it is not a guarantee of long-term support.

Getting Started: Commands and Configuration

For a developer, the setup cost is low. For a project maintainer, the cost is in defining the tool manifest. Each tool needs a package definition, and while Hermit likely has a library of common tools, not every tool will be covered. The README does not state the size of the package index, so you must check the docs or the repository for your specific tools.

The Self-Bootstrapping Trade-Off

Disk usage is another concern. Each project keeps its own binaries, so a developer working on five projects will have five copies of, say, the same version of Go. That is wasteful, but it is also what makes the isolation work. You cannot have true isolation without duplication. Hermit does not appear to offer a global cache or hard-link sharing, based on the repository description alone. If disk space is tight, this model may be a poor fit.

Alternatives: asdf, mise, and Docker

Docker is a completely different approach. Instead of managing tools on the host, you define a container image with all the tools and run your build inside it. Docker gives you absolute isolation, including the OS-level libraries, which Hermit does not. But Docker has a heavier runtime, and the container image needs to be built and maintained. Hermit is lighter weight because it runs natively on the host. The choice depends on whether you need OS-level isolation or just tool version isolation. Hermit is for the latter.

Maintenance and License

Upgrade cost is moderate. When a new version of Hermit itself is released, you need to update the global Hermit binary, but the per-project manifests are likely backward compatible. The rapid release cadence implies that you should watch the changelog before upgrading, especially if you have many projects. The self-bootstrapping nature means that each project will pick up the new Hermit behavior only when you re-run the bootstrap, so you have some control over when to adopt a new version.

Who Should Adopt It and What to Verify First

Before you commit, verify that Hermit's package index includes all the tools your project uses. Check the documentation for the list of supported tools. Then test the bootstrap on a clean machine to measure the time and disk usage. Also, check how Hermit handles tools that are not in the index. Does it allow custom package definitions? The README does not say. Finally, review the activation script to ensure it works with your shell (bash, zsh, fish) and with your CI system. The documentation site should have these details, but the README alone is not enough to make an informed decision.

Editorial conclusion

Adopt Hermit if your team or CI regularly fights over tool versions and you want a single, checked-in source of truth for every project's binaries. Skip it if you work on small, short-lived repos where the per-project download and disk overhead outweigh the consistency gain. Before adopting, verify that all your required tools are in the Hermit package index, that your build scripts can tolerate PATH being rewritten on shell startup, and that your CI runner can handle the initial bootstrap time for each project. The self-bootstrapping design is the core differentiator, but it only pays off when the project boundary is stable and the tool set is non-trivial.

Frequently asked questions

What is cashapp/hermit and what is it for?

Hermit installs tools for software projects in self-contained, isolated sets, so a team, its contributors and CI end up with the same tooling. It is written in Go, published by Square under Apache-2.0, and its full documentation lives at https://cashapp.github.io/hermit rather than in the README.

Where do I find the install instructions for cashapp/hermit?

The README contains no install command. It sends you to the documentation site at https://cashapp.github.io/hermit, and the repository has a docs/ directory at its root. How versions get published is a separate file, RELEASE.md.

What Go version does cashapp/hermit need to build?

The module declares go 1.26.0 as its language version and toolchain go1.27.1 as the toolchain it expects, so the floor and the expected toolchain are two versions apart. Building from source therefore needs more than the minimum language version.

Does cashapp/hermit unpack and read packages itself?

Yes. Its direct dependencies include saracen/go7z, ulikunitz/xz, klauspost/compress, blakesmith/ar, sassoftware/go-rpmutils and howett.net/plist, with gabriel-vasile/mimetype for content sniffing, so archive formats and package formats are handled inside the tool.

What is the skills/hermit directory in cashapp/hermit?

The README offers it as an AI coding agent skill for Hermit-managed repositories. The repository root also carries AGENTS.md and CLAUDE.md, which the README does not mention, alongside a Justfile and a .golangci.yml.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/cashapp-hermit.svg)](https://hysenlabs.com/projects/cashapp-hermit)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/cashapp-hermit.svg)](https://hysenlabs.com/projects/cashapp-hermit)

Was this useful?