Metadata
Release files for workercommon 0.5.3
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.3.tar.gz | 17.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| workercommon-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.1 kB
Release files / workercommon-0.5.3.tar.gz
| Download URL | workercommon-0.5.3.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d807b75432e33f353740cc44239d8997229f83ba6c9c123c9f12cd3658917dc
|
|
BLAKE2b-256 checksum How to use checksums |
70a0e020a8e06420b736e7ab251dc6ca90c5c1f6035fdde9db67b07b00f48b58
|
| 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.3-py3-none-any.whl
| Download URL | workercommon-0.5.3-py3-none-any.whl |
|---|---|
| Size | 22.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d406ecab39d63a98f02bea33c6b8d6c062f7844c29d96ce78cc887bb505f027
|
|
BLAKE2b-256 checksum How to use checksums |
57bd4093ae2ff50df8bc1a65562e7df1785dc4cd42416c173eef3ccb127fc337
|
| 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.3
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.