1 maintainer
Metadata
1 maintainer
Release files for understory-term 0.0.6
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-term-0.0.6.tar.gz | 17.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| understory_term-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.9 kB
Release files / understory-term-0.0.6.tar.gz
| Download URL | understory-term-0.0.6.tar.gz |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5142027eb3d4c0fd2e02228d322882e441d7a7b080096b3d89d959989c4267e
|
|
BLAKE2b-256 checksum How to use checksums |
55a2ab8d19ec8acde096e7a3008c4a77a3edc5cfbdc93dfb72ef9d82c2e18887
|
| 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_term-0.0.6-py3-none-any.whl
| Download URL | understory_term-0.0.6-py3-none-any.whl |
|---|---|
| Size | 17.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c94f56797715b091a28e477f4ec0b183b1511fa8e07164ea1cd3b8b95cd849e
|
|
BLAKE2b-256 checksum How to use checksums |
bb880845cb2615ff4e31e0961019869735fd91d3fa338faa9da79593bb80d099
|
| 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-term 0.0.6
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.
