Metadata
Release files for workercommon 0.5.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.5.1.tar.gz | 14.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| workercommon-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.4 kB
Release files / workercommon-0.5.1.tar.gz
| Download URL | workercommon-0.5.1.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9188248ea4c52c7b16b34b8974ee7f1f7b6fca45d97613ebb897a59b2b8f7e7a
|
|
BLAKE2b-256 checksum How to use checksums |
2a6dd828e154c5148b607baa8bbf4f6da7d912e6bfbabf730bd2033ca78d2029
|
| 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.1-py3-none-any.whl
| Download URL | workercommon-0.5.1-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f86b55a18980dd735d068265a97586d1a56093cb1011f804e1176148c997562f
|
|
BLAKE2b-256 checksum How to use checksums |
c8e60b115dd6633a805691ec3193e0d4eaff29ab33c0b21b9d5df0150faa2415
|
| 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.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.