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