Metadata
Release files for commitizen-cz-base 0.2.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 | Provenance | |
|---|---|---|---|---|
| commitizen-cz-base-0.2.0.tar.gz | 2.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| commitizen_cz_base-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.6 kB
Release files / commitizen-cz-base-0.2.0.tar.gz
| Download URL | commitizen-cz-base-0.2.0.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
878ea75e0601babdc35bb79f8305b67592cda47e85b994e186d29d5e9e62bbea
|
|
BLAKE2b-256 checksum How to use checksums |
5784110ccbd3c25e3491bbec9f71adb5f914639b64a44e7379bb9f4f8a76ca62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.16
|
Release files / commitizen_cz_base-0.2.0-py3-none-any.whl
| Download URL | commitizen_cz_base-0.2.0-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dffc618f7e61d03e01b31e4088027b214d5f9db4fb993a0b5d70d15c4e3910f0
|
|
BLAKE2b-256 checksum How to use checksums |
b37d291341c8cefcf99ea650387c0693c61916d64f267a482938c1982ae4b9f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.16
|
Security for commitizen-cz-base 0.2.0
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.