Metadata
Release files for workercommon 0.5.0
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.5.0.tar.gz | 14.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| workercommon-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.4 kB
Release files / workercommon-0.5.0.tar.gz
| Download URL | workercommon-0.5.0.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02b0749864f2e48c5aa6636c3ff9bed9dda174346e58b149ecaa697ec62bc3ce
|
|
BLAKE2b-256 checksum How to use checksums |
6c8a33cc4967b23e7fd5b4f4f32691f9aff83366b028ccd0349a4267fa611d3e
|
| 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.5.0-py3-none-any.whl
| Download URL | workercommon-0.5.0-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f73b8836cccbe567fc70d01cef8c6b5d4821bd5a11066e9027126977d6cb0a88
|
|
BLAKE2b-256 checksum How to use checksums |
da171bda828167b3d0fdba30059bcf063261b3288ac7f44a875cb7ca537a11c8
|
| 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.5.0
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.