Departure Mono's whole usage note is two lines about size and tracking

Two lines of rendering advice

The usage section is the shortest part of the file and the most operational. It says that for pixel-perfect results the font size should be set in increments of eleven pixels, and then it advises experimenting with tighter or wider tracking, which is the typographic term for letter spacing. That is the entire guidance: a size grid and a suggestion to adjust spacing. Everything else the file covers is installation and licensing. So a reader who wants to know whether this font will look right at a given size in a given editor has to work it out from the eleven pixel rule themselves, and a reader who wants to know whether it suits a retina display or a particular line height is not going to find it written down.

Two licences, and only one of them is about the font

The licences section is a two row table, and the split is the kind that matters. The font is under the SIL Open Font Licence, credited to one author, with the licence text living in the public assets directory. The site is under the MIT licence, credited to two authors, with its text at the root. The repository's own licence field records MIT. That is not a contradiction, it is a repository holding two things with two terms, but it does mean the value in the root licence file describes the website rather than the typeface. For anyone embedding the font in a product, the licence that applies is the first row, and the licence text to read is the one under the public assets directory rather than the one at the root.

Four install routes, three of them declarative

Installation is the longest section, and it covers four audiences. macOS users are pointed at a Homebrew cask:

brew install font-departure-mono

Nix users get two commands, one for the profile installer and one for the older environment installer, and both name the package by its canonical name rather than by a version:

# Here's an example on how to install it using `nix profile`
nix profile install github:NixOS/nixpkgs#departure-mono
# Here's an example on how to install it using `nix-env`
nix-env -iA nixos.departure-mono

NixOS users add it to the system configuration rather than installing it per machine:

{
  fonts.packages = [
    pkgs.departure-mono
  ];
}

Everyone else downloads the latest release. The two platform managers handle upgrades as part of installing, and the Nix commands install from the distribution's own package repository rather than from this project.

The repository is the website, not the typeface

The top level of the repository reads like a web project rather than a font project. There is a site entry point, a public directory, a source directory, a scripts directory, a build configuration and three separate TypeScript configuration files, plus a file holding the custom domain name for the hosted site and a lock file for the JavaScript package manager. The font's own assets sit under the public directory, which is also where its licence text lives. Nothing in the listing looks like glyph outlines, a font source format or an interpolation tool, so what a contributor would edit to change the typeface is not visible from the file list alone. The design history the README describes, in terms of early interfaces and film references, is therefore documented rather than reproducible from this repository.

The site is an editor, a canvas and a highlighter

The dependency list explains what the website does, and it does more than host a download link. A component kit and a reactive rendering library build the interface. A code editor appears in a dozen packages, with language support for nine languages including Go, Rust, SQL and Markdown, plus a highlighter and a bridge between the editor and the rendering library. A browser font editor is present, which is what turns the site into something you can try a typeface in rather than only read about. Two graphics libraries, one for shading languages on a canvas and one general purpose drawing library, plus a dimension measuring library, suggest rendered previews with measurements. Even the styling helper is installed under an alias rather than by its own name, which is the kind of detail a dependency audit surfaces.

Every build fetches a runner first

The scripts are arranged so that a build cannot start without an assembly step. There is a pre-development hook and a pre-build hook, and both run the same assemble target, which is not a local script but a command that asks the package manager to download and run a TypeScript runner against a script in the repository. Nothing in the development dependencies provides that runner, so the mechanism depends on the registry being reachable at the moment you start a development server or produce a build. The rest of the scripts are conventional: a dev server, a build that type-checks and then bundles, a formatter and a check mode for it, and a preview command. The consequence for a locked-down build environment is that the font's website cannot be built offline from a warm cache.

Versions, tags and the pages deploy

Two small inconsistencies run alongside the release history. The manifest carries a three part version while the newest release tag drops the patch component, and one earlier release carries no title at all while the others describe themselves. Neither matters much, but together they suggest a versioning habit that was never formalised. The site itself is deployed through a hosted pages tool listed as a development dependency, which matches the custom domain file at the root and explains why the homepage field points at a site rather than at the repository. The last commit to the default branch is dated 2026-09-13, and the newest release tag is from May 2025, so the site keeps moving while the typeface itself changes on a slower clock.

Editorial conclusion

Departure Mono fits someone who wants the small, deliberately limited pixel look of old terminals and film interfaces in a code editor, and who is willing to tune size and tracking to get it right. Check four things before adopting it: that 11 pixel increments suit your setup, since that is the only rendering guidance given, that you are comfortable with a typeface this small at your usual interface scale, which the two-line usage note leaves entirely to you, which licence applies to what, because the font and the site carry different ones and only the font matters if you redistribute it, and that the install route you pick is one that also upgrades, which the Homebrew cask is and a downloaded release is not.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. rektdeckard/departure-mono on GitHub
5. Releases