headroom: License Header Manager

[ bsd3, library, program, utils ] [ Propose Tags ]

Would you like to have nice, up-to-date license/copyright headers in your source code files but hate to manage them by hand? Then Headroom is the right tool for you! Now you can define your license header as Mustache template, put all the variables (such as author's name, year, etc.) into the YAML config file and Headroom will take care to add such license headers to all your source code files.

[Skip to Readme]


Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


Versions [RSS],,,,,,,,,,,,,,,
Change log CHANGELOG.md
Dependencies aeson, base (>=4.7 && <5), either, extra, file-embed, generic-data, headroom, http-client, http-types, microlens, microlens-aeson, microlens-th, modern-uri, mtl, mustache, optparse-applicative, pcre-heavy, pcre-light, persistent, persistent-sqlite, req, rio, string-interpolate, template-haskell, time, vcs-ignore, yaml [details]
License BSD-3-Clause
Copyright Copyright (c) 2019-2022 Vaclav Svejcar
Author Vaclav Svejcar
Maintainer vaclav.svejcar@gmail.com
Category Utils
Home page https://github.com/vaclavsvejcar/headroom
Bug tracker https://github.com/vaclavsvejcar/headroom/issues
Source repo head: git clone https://github.com/vaclavsvejcar/headroom
Uploaded by xwinus at 2022-01-20T16:26:05Z
Distributions NixOS:
Executables headroom
Downloads 3627 total (38 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2022-01-20 [all 1 reports]

Readme for headroom-

[back to package description]

Would you like to have nice, up-to-date license/copyright headers in your source code files but hate to manage them manually? Then Headroom is the right tool for you. Define your license header as Mustache template, put any template variables into YAML configuarion file, and you're ready to go!

Headroom also offers much more than just adding, replacing or dropping license headers. It can also update years in copyrights for you, provides content-aware templates for some source code file types, and much more!

Main Features

  • License Header Management - Add, replace or drop license headers in your source code files with a single command. What's more, contrary to many similar tools, Headroom allows you to also replace/drop headers that weren't previously generated by Headroom, using smart header auto-detection.
  • Powerful Customization - Default configuration should cover most use-cases, but if you need to put empty lines before/after generated header, use different comment style of headers, you can customize the configuration to match exactly your needs.
  • Built-in OSS License Headers - If you want to use license header for one of the popular OSS licenses, then Headroom can generate them for you - no need to search for them on web.
  • Automatic Initialization for OSS Projects - Setting up external tools like Headroom for your project can be boring. Fortunately, Headroom can initialize itself for your project, by generating configuration file and template files.
  • Content-aware Templates - for selected file types, Headroom exposes additional info about processed file using template variables, so you can use info like Java package name in your templates.
  • Copyright Year Updater - Headroom is good not only for basic license header management, but also for further processing of generated headers. Do you need to update years in your copyrights? No problem!


You can get Headroom via one of the following options:

  1. download pre-built binary for GNU/Linux or macOS (x64) from releases page
  2. install using Homebrew: brew install norcane/tools/headroom
  3. build from source code - see project microsite for more details


Here is the list of projects using Headroom. If you're using Headroom and aren't on the list, feel free to submit new issue or pull request.



Running microsite locally

If you need to show microsite documetation for unreleased version of Headroom (e.g. for master branch), you can run it locally using MkDocs tool:

$ cd doc/microsite/
$ mkdcs serve

Documentation is then available on