The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for copkmeans-ht 1.5
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 | |
|---|---|---|---|---|
| copkmeans-ht-1.5.tar.gz | 6.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| copkmeans_ht-1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.8 kB
Release files / copkmeans-ht-1.5.tar.gz
| Download URL | copkmeans-ht-1.5.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf39dfc1a7ac609397ff099207df936921ddbce451dd63e72177094861fd4446
|
|
BLAKE2b-256 checksum How to use checksums |
9bc63ee8b1eb50d564490b91c973aa494d62c1f2f5404ce6659917ac3aa1a0ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.5
|
Release files / copkmeans_ht-1.5-py3-none-any.whl
| Download URL | copkmeans_ht-1.5-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5578993b8e0c458236d6bc14aecca3daff312fc0dca47f89ad8dc889fe4b1657
|
|
BLAKE2b-256 checksum How to use checksums |
95faab8d5e9cf80336ecb9a59f275d68e3c06a45a5c9451def14cb28c932b0ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.5
|
Security for copkmeans-ht 1.5
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.
