Metadata
Release files for data-disaggregation 0.12.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 | |
|---|---|---|---|---|
| data_disaggregation-0.12.0.tar.gz | 13.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| data_disaggregation-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.1 kB
Release files / data_disaggregation-0.12.0.tar.gz
| Download URL | data_disaggregation-0.12.0.tar.gz |
|---|---|
| Size | 13.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6c61eb5eaa9851efec361474827f09a57d118a1074198e9f46716daf3d8932a0
|
|
BLAKE2b-256 checksum How to use checksums |
61702bfafd131fb4b85d02e612c7b8e73e44bd624dea162ea1a01881855e5d9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / data_disaggregation-0.12.0-py3-none-any.whl
| Download URL | data_disaggregation-0.12.0-py3-none-any.whl |
|---|---|
| Size | 11.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1ec56d24b9e46ad693f8dc23525240f583e315b82b223ef51947a8e57a7be2e
|
|
BLAKE2b-256 checksum How to use checksums |
ac6c5bf861d8b6b44c381572a74c262c4cee5682dea466c2965475f9910e23a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for data-disaggregation 0.12.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.