Metadata
Release files for understory-web 0.0.22
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 | |
|---|---|---|---|---|
| understory-web-0.0.22.tar.gz | 340.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| understory_web-0.0.22-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 694.1 kB
Release files / understory-web-0.0.22.tar.gz
| Download URL | understory-web-0.0.22.tar.gz |
|---|---|
| Size | 340.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8bcd7f8972a544900a9625bc2c0d72add8c663c0ae86a11df6c90134a3054d03
|
|
BLAKE2b-256 checksum How to use checksums |
1fbe3b272d7c1e58b17f2182485592a54b939c6beb76c635c2a2efa90f9ca59f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.9.1 Linux/4.19.0-17-amd64
|
Release files / understory_web-0.0.22-py3-none-any.whl
| Download URL | understory_web-0.0.22-py3-none-any.whl |
|---|---|
| Size | 353.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ebff4fc4488170129b24e03ede8cb631225661f3c04e788a4b8f6aac65b4a8c3
|
|
BLAKE2b-256 checksum How to use checksums |
120b4c777ff840574209fc6631ce33a1bde1dcd3ac8b7bb89521953124ac7ebf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.9.1 Linux/4.19.0-17-amd64
|
Security for understory-web 0.0.22
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.