Metadata
Release files for setuptools-git-version-cc 3.0.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 | |
|---|---|---|---|---|
| setuptools-git-version-cc-3.0.4.tar.gz | 3.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| setuptools_git_version_cc-3.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.0 kB
Release files / setuptools-git-version-cc-3.0.4.tar.gz
| Download URL | setuptools-git-version-cc-3.0.4.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
acdf0fd0303e4de749c29195cca16ac2ca59934fbc8d18e81d12d527ce3795c8
|
|
BLAKE2b-256 checksum How to use checksums |
11716cf10ab26e58476ba87fe166e9c6cb3eda2069882204e2c8ca86c082d688
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Release files / setuptools_git_version_cc-3.0.4-py3-none-any.whl
| Download URL | setuptools_git_version_cc-3.0.4-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f6d8c63def07f92ba26dd93c00e4366ae85db3eaec481d372f99e746a272dca
|
|
BLAKE2b-256 checksum How to use checksums |
bf2890db6bb9f3830a9a35a433dc45ca73242f63863aaf07620e5bd819c3140f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Security for setuptools-git-version-cc 3.0.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.