Pre commit to update the copyright header
pre-commit hook used to check if the copyright is up to date (using the Git history).
Adding to your .pre-commit-config.yaml
repos:
- repo: https://github.com/sbrunner/pre-commit-copyright
rev: <version> # Use the ref you want to point at
hooks:
- id: copyright
Metadata
Release files for pre-commit-copyright 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pre_commit_copyright-0.1.4.tar.gz | 2.9 kB | Without provenance | Details for pre_commit_copyright-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pre_commit_copyright-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for pre_commit_copyright-0.1.4-py3-none-any.whl |
Total release size: 5.8 kB
Release files / pre_commit_copyright-0.1.4.tar.gz
| Download URL | pre_commit_copyright-0.1.4.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d110bea0f5c015867b30f4c6edb4a6a9626d4edaf6399d9302a5f6fb2afd0ec
|
|
BLAKE2b-256 checksum How to use checksums |
dc419a674a19bd43d5328c6da4a8da977191c74391dd4095e2edf67185297736
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / pre_commit_copyright-0.1.4-py3-none-any.whl
| Download URL | pre_commit_copyright-0.1.4-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3ac34c38549abe9bc42f7d100efedb98a59ab12fcac97d32f6d3b080c6a482f
|
|
BLAKE2b-256 checksum How to use checksums |
65fdb15c4a544d49fa2f7474de27f0a904a31b8550363c7b0400efeef806534b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for pre-commit-copyright 0.1.4
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.