The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for ai-worker 8.0.2
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 | |
|---|---|---|---|---|
| ai_worker-8.0.2.tar.gz | 31.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai_worker-8.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.6 kB
Release files / ai_worker-8.0.2.tar.gz
| Download URL | ai_worker-8.0.2.tar.gz |
|---|---|
| Size | 31.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af2d2afb8b8fb7fa5145047b87fc1bf0a1bdb11323cc246ce954ac7748f2bff0
|
|
BLAKE2b-256 checksum How to use checksums |
e244a4745713071b0a8887c7a277d78a09abb6eaf2ed98f7e70265c246c5e049
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.6
|
Release files / ai_worker-8.0.2-py3-none-any.whl
| Download URL | ai_worker-8.0.2-py3-none-any.whl |
|---|---|
| Size | 27.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
597deb440d36d9f350f4095223510c32116a5d7ea48a830101e407ed8a03bd0e
|
|
BLAKE2b-256 checksum How to use checksums |
fc301f5b71804dfcd76cbe2c83c4bad968ee4a032636a548b5cccdf7e57f6521
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.6
|
Security for ai-worker 8.0.2
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.
