Metadata
Release files for workercommon 0.6.1
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 | |
|---|---|---|---|---|
| workercommon-0.6.1.tar.gz | 17.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| workercommon-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.3 kB
Release files / workercommon-0.6.1.tar.gz
| Download URL | workercommon-0.6.1.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba05b548771db3a915bc0627acf90009ace29ab16f2aaa77fe6dd56a87500d11
|
|
BLAKE2b-256 checksum How to use checksums |
038e8d7512092903254dc4b0ecb3d4712fb9ddcc9278d56725451243b63db884
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / workercommon-0.6.1-py3-none-any.whl
| Download URL | workercommon-0.6.1-py3-none-any.whl |
|---|---|
| Size | 22.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a64763bd98418db444628ab66f1c1ccf6bfab552a600c922ef11c49acc8c0f01
|
|
BLAKE2b-256 checksum How to use checksums |
8e6d67c268e051317d9a3d66875256e5dc2d078eafe04df656eeaf1ab485c6a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for workercommon 0.6.1
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.