1 maintainer
Metadata
1 maintainer
Release files for ctyun-bootstrap 1.5.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 | |
|---|---|---|---|---|
| ctyun_bootstrap-1.5.0.tar.gz | 28.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ctyun_bootstrap-1.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 45.0 kB
Release files / ctyun_bootstrap-1.5.0.tar.gz
| Download URL | ctyun_bootstrap-1.5.0.tar.gz |
|---|---|
| Size | 28.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b410c652c2b0c8da79663cbbf0e8a1982e49d329ee10edd3770223652c2321f
|
|
BLAKE2b-256 checksum How to use checksums |
9ab1ed9da008b9422473cc2fab7ec992fa123d11bb3e461f5ebb3ff7c7548c03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.13
|
Release files / ctyun_bootstrap-1.5.0-py3-none-any.whl
| Download URL | ctyun_bootstrap-1.5.0-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49b0b969222f6e7e6a741944ea45f880a34d6a7fad2016e46a978b2d8ef5193d
|
|
BLAKE2b-256 checksum How to use checksums |
cff76e6c276cd2638317bd5373fd88bf11e1c0fc2ee58c2328ecde93c271829e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.13
|
Security for ctyun-bootstrap 1.5.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.
