1 maintainer
Metadata
1 maintainer
Release files for vease-back 1.16.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 | |
|---|---|---|---|---|
| vease_back-1.16.0.tar.gz | 13.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vease_back-1.16.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.3 kB
Release files / vease_back-1.16.0.tar.gz
| Download URL | vease_back-1.16.0.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
884b38028f73574bf6116f3aca252b1889521c17138856c2c9678a26cc70e08f
|
|
BLAKE2b-256 checksum How to use checksums |
44c6ddbdd500d228999e0f7abde05b2985bb9d1ffa34ef8bc3b0da6eb5f2be04
|
| 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.0-py3-none-any.whl
| Download URL | vease_back-1.16.0-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cd59be41f0daff76c37fb4b4b919d626937035a1c07482170ba112e61d32d34
|
|
BLAKE2b-256 checksum How to use checksums |
025209373dbb1bc0eed72640c066d1833119c7c5cfe87e1ec2f0e76132203690
|
| 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.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.
