The author of this package has not provided a project description
Metadata
Release files for quadkit-resilience 0.0.1
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 | |
|---|---|---|---|---|
| quadkit_resilience-0.0.1.tar.gz | 388 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quadkit_resilience-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 kB
Release files / quadkit_resilience-0.0.1.tar.gz
| Download URL | quadkit_resilience-0.0.1.tar.gz |
|---|---|
| Size | 388 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7780eede0a12375c7a42ba815b4d29a344fe2b185a7726be5606717e83151e6
|
|
BLAKE2b-256 checksum How to use checksums |
b783a63ddcf484f37bea5ec43a8cd1140c339ab357529349b64735ba969b6db3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / quadkit_resilience-0.0.1-py3-none-any.whl
| Download URL | quadkit_resilience-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21ca7168d2a5c8116989fadf16ea0300c86e89c09f5ba25da65ded2400f90c8c
|
|
BLAKE2b-256 checksum How to use checksums |
35244668fe8e01cf807ca2cdbc6a32a4b932a186562c0bc990b4fe83d3aa7b1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for quadkit-resilience 0.0.1
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.