The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for macore-client 0.1.34
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.34.tar.gz | 5.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| macore_client-0.1.34-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.8 kB
Release files / macore_client-0.1.34.tar.gz
| Download URL | macore_client-0.1.34.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05ac046ce2b8babb8f5a4b17ae6c17ca3cade1b3777af233ee761a0c782b7eb3
|
|
BLAKE2b-256 checksum How to use checksums |
417bf9d0b57492bb2113003eb84941a6e7d5923baeb4e298fe010efd7cb3da06
|
| 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.34-py3-none-any.whl
| Download URL | macore_client-0.1.34-py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e0b0ce209ee168c68756676e074365fd9fa06aa3c943171b0126a61dc5b7905e
|
|
BLAKE2b-256 checksum How to use checksums |
65c6d7bbf5232af1f5c923753e9e2661359e2f04d10f593ffabf7edadc97d454
|
| 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.34
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.
