Metadata
Release files for understory-fx 0.0.5
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-fx-0.0.5.tar.gz | 16.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| understory_fx-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.1 kB
Release files / understory-fx-0.0.5.tar.gz
| Download URL | understory-fx-0.0.5.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4158ea975ab7672b7c8ec22e4b86a38124f061a95af9d9538c6d36e846047a98
|
|
BLAKE2b-256 checksum How to use checksums |
bb311a15bd5e676b7629caa6f039154d4e2ddcf6543b9569d43e40b888e05767
|
| 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-16-amd64
|
Release files / understory_fx-0.0.5-py3-none-any.whl
| Download URL | understory_fx-0.0.5-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8838c91208b33860e677f613cecea08777eb89451eac6712775768ed0b96acc
|
|
BLAKE2b-256 checksum How to use checksums |
603a829e70cc1960efe9a0579311ff15438a726816b38ebe29d986b92a357222
|
| 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-16-amd64
|
Security for understory-fx 0.0.5
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.