1 maintainer
Metadata
1 maintainer
Release files for dagster-cloud-backend 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 | |
|---|---|---|---|---|
| dagster_cloud_backend-0.1.0.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dagster_cloud_backend-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.7 kB
Release files / dagster_cloud_backend-0.1.0.tar.gz
| Download URL | dagster_cloud_backend-0.1.0.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c36208ce8e6f5d3c7d47f2c7fa78b46dd5d9e4dd072bf5852bdf39832cd29240
|
|
BLAKE2b-256 checksum How to use checksums |
a304cba2ac5323c53bcfefc88b3145725434e83a5fa487de0e5ad1bb073df0bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / dagster_cloud_backend-0.1.0-py3-none-any.whl
| Download URL | dagster_cloud_backend-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86a98cd8e5876080f60734f07477cefad25d76ff857dd4f51c7e0e7907cd6e83
|
|
BLAKE2b-256 checksum How to use checksums |
3348349beaddbeba9992c84b8d97c7221e48efe5e4c9bc0928b4de6fca458d00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for dagster-cloud-backend 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.
