The author of this package has not provided a project description
5 maintainers
Metadata
5 maintainers
Release files for kfp-notebook 4.1.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 | |
|---|---|---|---|---|
| kfp_notebook-4.1.1.tar.gz | 9.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kfp_notebook-4.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.3 kB
Release files / kfp_notebook-4.1.1.tar.gz
| Download URL | kfp_notebook-4.1.1.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f19a82a931f33e4d2363eb05eda2800893c435fbea901562581dae33a6b714a5
|
|
BLAKE2b-256 checksum How to use checksums |
7f46f2e35ca7445ac536d3900f4b5546685b2f880732812919a319bd393082ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / kfp_notebook-4.1.1-py3-none-any.whl
| Download URL | kfp_notebook-4.1.1-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f95b34c193325a080a76dd476434186999ce289571ddc19b4f397bc6959bfb7
|
|
BLAKE2b-256 checksum How to use checksums |
051a36a87690c97a6ed4ddc39227f3ca20fe1ce93230f1aa2990ad7ee846d0bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for kfp-notebook 4.1.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.
