This release is a pre-release and may not be stable for production use.
1 maintainer
Metadata
1 maintainer
Release files for vease-back 1.15.3rc1
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 | |
|---|---|---|---|---|
| vease_back-1.15.3rc1.tar.gz | 13.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vease_back-1.15.3rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / vease_back-1.15.3rc1.tar.gz
| Download URL | vease_back-1.15.3rc1.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f106b2d12f3cbe339245e3a792bcb7cccd628b494d4f7be9f602697eb375fa51
|
|
BLAKE2b-256 checksum How to use checksums |
7ffa99c50fa4c391d3556a1aef33eb09b2ff25ab4b5b8136f20bfc0616695575
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.15
|
Release files / vease_back-1.15.3rc1-py3-none-any.whl
| Download URL | vease_back-1.15.3rc1-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b183909119fd1d86d5b82be876823ff710494a699c5a74f415d09709947f39f3
|
|
BLAKE2b-256 checksum How to use checksums |
cd717fb8fb5c13c47ef3d51e21908356a4763203926de65b2ef785bfabe89614
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.15
|
Security for vease-back 1.15.3rc1
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.
