Set up game-winning headers!
Chipshot helps standardize header information in software development files.
Its target goal is to ensure that copyright dates are standardized and that licensing information is present.
It supports a wide range of file formats, including source code and documentation formats. It purposely does not support configuration file formats by default (such as TOML, INI, or YAML) but can be configured to support those, too.
Sample configuration
Create a file named .chipshot.toml with the following content:
[chipshot]
template = """
Copyright 2021-{{ year }} Developer or Company
Released under the terms of the MIT license.
SPDX-License-Identifier: MIT
"""You can then run chipshot path1 path2 to see what files will be modified. If you’re satisfied, run chipshot --update path1 path2 to update the files.
Pre-commit hooks
Chipshot offers two pre-commit hooks to help you manage your projects:
check-headers
update-headers
Here’s a sample configuration for ensuring your files have correct headers:
# Filename: .pre-commit-config.yaml
repos:
- repo: 'https://github.com/kurtmckee/chipshot'
rev: 'v0.9.0'
hooks:
- id: 'update-headers'1 maintainer
Release files for chipshot 0.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| chipshot-0.9.0.tar.gz | 13.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chipshot-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.0 kB
Release files / chipshot-0.9.0.tar.gz
| Download URL | chipshot-0.9.0.tar.gz |
|---|---|
| Size | 13.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0fd5eff8545321d84f6cbbce5740e2d3de518582b9d8da4b7eb5e121bbc68a5f
|
|
BLAKE2b-256 checksum How to use checksums |
cf48a690c9ef74da52e506a369b4baf7831cd7ce588e0ab021da96b55ea2e9cb
|
| 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 Feb 7, 2026.
Transparency logRelease files / chipshot-0.9.0-py3-none-any.whl
| Download URL | chipshot-0.9.0-py3-none-any.whl |
|---|---|
| Size | 20.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c7238e91f3cd5a02c70a1157a5ab532a95b5ba05247ae15efbcf4bbd5b42e1ee
|
|
BLAKE2b-256 checksum How to use checksums |
33d135c5d7f6a8226be1a29c89255ce5fd26fbe8dabb5e5dc8f4acdd03da4bc3
|
| 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 Feb 7, 2026.
Transparency log
