1 maintainer
Metadata
1 maintainer
Release files for itlubber-automl 0.1.3
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 | |
|---|---|---|---|---|
| itlubber_automl-0.1.3.tar.gz | 10.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| itlubber_automl-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.1 kB
Release files / itlubber_automl-0.1.3.tar.gz
| Download URL | itlubber_automl-0.1.3.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cdec5335fa4351b6ebe3fe76f812441e376b558ad41c25dac280dea095fd54ba
|
|
BLAKE2b-256 checksum How to use checksums |
1f9834b4496c33a76cb6c513f5109bfddb466db846e8d0a6066ee9f2d04d00cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.8
|
Release files / itlubber_automl-0.1.3-py3-none-any.whl
| Download URL | itlubber_automl-0.1.3-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b0ea13ee20775f48187887e425e564621a35a321dda5e9c4ccb936ea4f6a307
|
|
BLAKE2b-256 checksum How to use checksums |
0d1234c414c3c4530d2f8c73dd2c9836e875f1df2aeb291abf6acef8b85011e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.8
|
Security for itlubber-automl 0.1.3
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.
