Skip to main content

add-license-header

A tool for automatically adding your license as a header in your source code.

Installation

pip install add-license-header

pre-commit hook

See pre-commit for instructions.

Sample with license template file:

- repo: https://github.com/arkinmodi/add-license-header
  rev: v2.4.1
  hooks:
      - id: add-license-header
        args:
            - --license-file
            - MIT-LICENSE.template

Sample with inline license template:

- repo: https://github.com/arkinmodi/add-license-header
  rev: v2.4.1
  hooks:
      - id: add-license-header
        args:
            - --license
            - |
                MIT License

                Copyright (c) $create_year $author_name
                ...

Template Options

You can use template markers to dynamically change your license.

Template Marker Default CLI Flag
$author_name Empty string. --author-name
$create_year Introduction into git history. If not managed by git, then the current year. --create-year
$edit_year Current year. --edit-year
$year_delimiter ", " --year-delimiter

For example:

MIT License

Copyright (c) $create_year $author_name

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

What does it do?

$ cat example.py
print("Hello World")

$ add-license-header \
    --license-file MIT-LICENSE.template \
    --author-name 'Arkin Modi' \
    --create-year 2023 \
    example.py
updating license in example.py

$ cat example.py
# LICENSE HEADER MANAGED BY add-license-header
#
# MIT License
#
# Copyright (c) 2023 Arkin Modi
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in all
# copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#

print("Hello World")

Managed vs Un-Managed

In managed mode (the default), the license header will contain LICENSE HEADER MANAGED BY add-license-header in first line of the comment block. This enabled the tool to be able to accurately find the license header and allows you to place the license header anywhere in the file.

In unmanaged mode, enabled with the --unmanaged flag, the top-most comment block will be assumed to be the license header. Block comments that have been condensed to a single will not be treated as a block comment. This mode is less predictable and may require manual correction when first adding the license header.

Metadata

Release files for add-license-header 2.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for add-license-header 2.4.1
File Size Uploaded
add_license_header-2.4.1.tar.gz 6.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for add-license-header 2.4.1
File Interpreter ABI Platform
add_license_header-2.4.1-py3-none-any.whl Python 3 none any Details

Total release size: 14.2 kB

Release files / add_license_header-2.4.1.tar.gz

Download URL add_license_header-2.4.1.tar.gz
Size 6.5 kB
Tags Source
SHA-256 checksum
How to use checksums
7fe44b43b6bd4fdfe107720ed3b69961b3d059bf271133b48d68bfaec5265b2c
BLAKE2b-256 checksum
How to use checksums
101430d5503a0ef4091b14b549c3a3843641dad6150f74d75e02dab67da53765
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 25, 2026.

Transparency log

Release files / add_license_header-2.4.1-py3-none-any.whl

Download URL add_license_header-2.4.1-py3-none-any.whl
Size 7.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c1fdb49ca2bddf0bcd7a428f71fad30e682560d4b009ea8ba40e14bd7a83de73
BLAKE2b-256 checksum
How to use checksums
3d1b7b591ca2d5f5c02715c0f201b1122593b6a42897ff5ee40b4bd73e8bd3cd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2.4.1 This release

2 release files

2.4.0

2 release files

2.3.1

2 release files

2.3.0

2 release files

2.2.0

2 release files

2.1.0

2 release files

2.0.4

2 release files

2.0.3

2 release files

2.0.2

2 release files

2.0.1

2 release files

2.0.0

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page