The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for macore-client 0.1.32
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.32.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| macore_client-0.1.32-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.0 kB
Release files / macore_client-0.1.32.tar.gz
| Download URL | macore_client-0.1.32.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af376136753acbf97c265a2f24ac713dd25b7eb0cd0ea289c1d70928c6e83b2c
|
|
BLAKE2b-256 checksum How to use checksums |
3bed76dfce47bdedadf70558e36c3a95782cfb0fae8a9ae1b618982c0b650630
|
| 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.32-py3-none-any.whl
| Download URL | macore_client-0.1.32-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02ef462783aa14cad744917dc825d59ed9d3115d3a013cf50efe757e960297be
|
|
BLAKE2b-256 checksum How to use checksums |
a399e18a0665bdd4892b32ba44f68ca2ce031f948ebc4b7822a38fb330701837
|
| 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.32
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.
