Metadata
Release files for cargo-vcs 2.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 | |
|---|---|---|---|---|
| cargo-vcs-2.4.tar.gz | 2.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cargo_vcs-2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.2 kB
Release files / cargo-vcs-2.4.tar.gz
| Download URL | cargo-vcs-2.4.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05cd321dad06d24d25f74bcd7177f0a766a71d44aa53b6524ac6aeaf896ede9f
|
|
BLAKE2b-256 checksum How to use checksums |
e5e9c8b394e62b714c6e9be72d1d3a512fca5cac9c5ce0c740874f6c4ece04b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.25.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.52.0 CPython/3.8.2
|
Release files / cargo_vcs-2.4-py3-none-any.whl
| Download URL | cargo_vcs-2.4-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f83a8c8abbb4a0636c42c6016c33820d8dbbd9461234b1c214625e86e9cf15e4
|
|
BLAKE2b-256 checksum How to use checksums |
a07e866b5f2db0239c994e8afebad76c966210755f48999e453c60f47632f2c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.25.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.52.0 CPython/3.8.2
|
Security for cargo-vcs 2.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.