Metadata
Release files for barbthroat 0.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 | |
|---|---|---|---|---|
| barbthroat-0.1.2.tar.gz | 20.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| barbthroat-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.7 kB
Release files / barbthroat-0.1.2.tar.gz
| Download URL | barbthroat-0.1.2.tar.gz |
|---|---|
| Size | 20.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
684d61accabe175bc8f10a7fb31c0c6359faf6f66bcde14cd2004c89a5abc1b8
|
|
BLAKE2b-256 checksum How to use checksums |
f58c678af2bc8d5377d9f2e2e8aa3b37786d39bf49e2a3db8f876779d6e8c168
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.1 CPython/3.8.16 Linux/5.15.79.1-microsoft-standard-WSL2
|
Release files / barbthroat-0.1.2-py3-none-any.whl
| Download URL | barbthroat-0.1.2-py3-none-any.whl |
|---|---|
| Size | 27.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf965464fa9e119bfdad9719da914d999a04a23ae6752dbc795abe8b61e967b7
|
|
BLAKE2b-256 checksum How to use checksums |
1c0cd0e7776588045f74cb98467e1315cee45d9f3f3e234d0539aec0fb422935
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.1 CPython/3.8.16 Linux/5.15.79.1-microsoft-standard-WSL2
|
Security for barbthroat 0.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.