The author of this package has not provided a project description
Metadata
Release files for mlx-cuda-15 0.0.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 | |
|---|---|---|---|---|
| mlx_cuda_15-0.0.0.tar.gz | 1.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mlx_cuda_15-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 kB
Release files / mlx_cuda_15-0.0.0.tar.gz
| Download URL | mlx_cuda_15-0.0.0.tar.gz |
|---|---|
| Size | 1.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8238be2bf5c15bf6202008c3dc3b033346811131075d91a1c9007902c478c608
|
|
BLAKE2b-256 checksum How to use checksums |
dbc36fc78cae2300eaf4af7424f35429ca4eea7d10ec5c685392de2dcca22400
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.17
|
Release files / mlx_cuda_15-0.0.0-py3-none-any.whl
| Download URL | mlx_cuda_15-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82112647d273ead889a8656fee040456aedc677871bab0fc62d8a27d3e12516f
|
|
BLAKE2b-256 checksum How to use checksums |
b67a4f59f33a2b2036b1987ae804d5e1b9e3f998bf3dc8034c2a970c3e659067
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.17
|
Security for mlx-cuda-15 0.0.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.