A package to use for automated machine learning using gui or without care about code
1 maintainer
Metadata
1 maintainer
Release files for automlll 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 | |
|---|---|---|---|---|
| automlll-0.0.1.tar.gz | 3.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| automlll-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.3 kB
Release files / automlll-0.0.1.tar.gz
| Download URL | automlll-0.0.1.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
30f615d5f72ebd7848630c26723a1200d4cd728aace48cbafd419ce6299a7ac6
|
|
BLAKE2b-256 checksum How to use checksums |
077dc073648005b9acf3e1445d886f434cb707d7b33da60db51817844d444d21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / automlll-0.0.1-py3-none-any.whl
| Download URL | automlll-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e766ef42ce92514c372a89370f00de6ff8eb5e4cdd5e4e4a5cbf4501ccae902c
|
|
BLAKE2b-256 checksum How to use checksums |
0a053cb58057bd6c0201abad07f49ac3cf079d22eae15be5e5d324bcb300cdb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for automlll 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.
