The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aimlpkit 0.3.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 | |
|---|---|---|---|---|
| aimlpkit-0.3.0.tar.gz | 6.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aimlpkit-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / aimlpkit-0.3.0.tar.gz
| Download URL | aimlpkit-0.3.0.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
846cad008fdaa452e020f8df8f0e5ad182dffb1ee5b6eeae20ddace57363a51c
|
|
BLAKE2b-256 checksum How to use checksums |
20c27f511d52f6fe0ac240a458707af5b42bc40f80461a5b151fb9eba73e7c05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / aimlpkit-0.3.0-py3-none-any.whl
| Download URL | aimlpkit-0.3.0-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ada29429d595e5e639e3b08f71672c23c555ea48bf2bf0af0429a42375cbb5f
|
|
BLAKE2b-256 checksum How to use checksums |
c04b850f2600bc67b8d1f0554a30ec5c5f9b554662e606223810aa1f68254186
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for aimlpkit 0.3.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.
