goatbeat-celery
Celery submitter for Goatbeat. Part of Goatbeat.
1 maintainer
Metadata
1 maintainer
Release files for goatbeat-celery 0.1.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 | |
|---|---|---|---|---|
| goatbeat_celery-0.1.0.tar.gz | 3.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| goatbeat_celery-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 kB
Release files / goatbeat_celery-0.1.0.tar.gz
| Download URL | goatbeat_celery-0.1.0.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc50838d4956db45877fca349258190bc5fe35b0cce927b6d4a197e69d81b8e0
|
|
BLAKE2b-256 checksum How to use checksums |
c007427f755406a94bbfdefb5aa430e885263f19859d290d33c31364cb318189
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / goatbeat_celery-0.1.0-py3-none-any.whl
| Download URL | goatbeat_celery-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
034a1a0c79d27332c92e674690b56e172605323ca0c152a39e315128d62f5113
|
|
BLAKE2b-256 checksum How to use checksums |
ef0e42346d6b5d1661df90cc939828ac3f49dfad6d36dfb873ddbfef0e910aaf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for goatbeat-celery 0.1.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.
