The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for macore-client 0.1.31
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 | |
|---|---|---|---|---|
| macore_client-0.1.31.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| macore_client-0.1.31-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / macore_client-0.1.31.tar.gz
| Download URL | macore_client-0.1.31.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
139174447766c9aca74f1a8c0c8c36d4319b0a751222cd15fbfbe1726e43ec55
|
|
BLAKE2b-256 checksum How to use checksums |
4d03743805daec96ddf97568f4c7d88559cfb37e47785eabd8c3966105bff62f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / macore_client-0.1.31-py3-none-any.whl
| Download URL | macore_client-0.1.31-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c20cc0d87a40a672cb74e043826d5652020540b02de40943ba6409f0b65e98b3
|
|
BLAKE2b-256 checksum How to use checksums |
41b5d9b37c735626b0f5fd2d48e67c78cdd790bbae693cdd4dbc4a49cba5b70e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for macore-client 0.1.31
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.
