Metadata
Release files for workercommon 0.6.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.6.0.tar.gz | 17.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| workercommon-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.3 kB
Release files / workercommon-0.6.0.tar.gz
| Download URL | workercommon-0.6.0.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd799fc63b11904cb9fd30287c3e5178d45fda0a6caae3a23acada40ff66687d
|
|
BLAKE2b-256 checksum How to use checksums |
06f1da6c99e49f00f849e291b8a240fa000b62af90ba2473e1ca4e5a0b176868
|
| 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.0-py3-none-any.whl
| Download URL | workercommon-0.6.0-py3-none-any.whl |
|---|---|
| Size | 22.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2d406919ab33d95876685c19cb2ee62d9412c9fddc7a6d2e1369cf850a662a6
|
|
BLAKE2b-256 checksum How to use checksums |
903fbbaf9445a75dc69a90ec873cc5e57fb8368a817f9e88d74d8f6b9205d28f
|
| 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.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.