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.16.0rc1
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.16.0rc1.tar.gz | 13.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vease_back-1.16.0rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / vease_back-1.16.0rc1.tar.gz
| Download URL | vease_back-1.16.0rc1.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d0457c1a649f64972d1d25ea2deee1af8488353084c57915cc2600a977f6b95
|
|
BLAKE2b-256 checksum How to use checksums |
f8003a8ef99b2211ee9563090068ffbd1221e47af7f110f53f434d581ffa669a
|
| 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.16.0rc1-py3-none-any.whl
| Download URL | vease_back-1.16.0rc1-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd11749c7affc453b313c0919e65a4aae20514c7c56d7eeeae80a24522a34bfd
|
|
BLAKE2b-256 checksum How to use checksums |
f4a4a57d50be3b4e9140ecbc7432122b0c73f37a2d4970a96b096986e6e0a37b
|
| 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.16.0rc1
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.
