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.0rc2
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.0rc2.tar.gz | 13.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vease_back-1.16.0rc2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / vease_back-1.16.0rc2.tar.gz
| Download URL | vease_back-1.16.0rc2.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8870427147cb4732c814aa9987dcf8699a618dab7997c711636d2ca2132440a6
|
|
BLAKE2b-256 checksum How to use checksums |
4cf9b0287c09a986ba00f34d01a5631655b7c35daea5ac6f119944e63c364c84
|
| 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.0rc2-py3-none-any.whl
| Download URL | vease_back-1.16.0rc2-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
601b8933e7e0715d47fb24142eb46fb75209830deefb448759b2dd5cd26008c6
|
|
BLAKE2b-256 checksum How to use checksums |
2a08414053592f0528455c30a55cd1cc8c73330414c63f658227ea0e1ebb4f41
|
| 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.0rc2
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.
