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.1rc2
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.1rc2.tar.gz | 13.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vease_back-1.16.1rc2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / vease_back-1.16.1rc2.tar.gz
| Download URL | vease_back-1.16.1rc2.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6a571377629e54caf5f42c62b7f2899952caa21db0b94ad8e950362cb2a06cf
|
|
BLAKE2b-256 checksum How to use checksums |
94d81e0f71405514a5b99fb48f81273f1e166b61236d0bc116688ca71a9257f2
|
| 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.1rc2-py3-none-any.whl
| Download URL | vease_back-1.16.1rc2-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef54d664906cd339b70b36c9fad21a94c7d28cf912f79e7b67a09265dc509b99
|
|
BLAKE2b-256 checksum How to use checksums |
88b450a55680837ca6d6468a4cacc41a99a486ba3a17ff1cc5b283cb3d6bc221
|
| 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.1rc2
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.
