Metadata
Release files for vape-base-extension 1.1.2
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 | |
|---|---|---|---|---|
| vape_base_extension-1.1.2.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vape_base_extension-1.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.0 kB
Release files / vape_base_extension-1.1.2.tar.gz
| Download URL | vape_base_extension-1.1.2.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5cec611f017ac263ed6cdbd76694faa6ea854756da4d0a158708689f805fc6b0
|
|
BLAKE2b-256 checksum How to use checksums |
d8f9ce9c58722f0b173285d5f9fedc85ee86f772212ce00f49edca2e3fb22b27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.1 CPython/3.11.3
|
Release files / vape_base_extension-1.1.2-py3-none-any.whl
| Download URL | vape_base_extension-1.1.2-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13e6406b4b461d3ae26737dcbbd5e291f664bbf0bdad2b5c877cdfde7387e0bc
|
|
BLAKE2b-256 checksum How to use checksums |
7dd66338ae49898830a72344b92b630835c593cdc10324611308434c7121745d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.1 CPython/3.11.3
|
Security for vape-base-extension 1.1.2
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.