integral-client
Metadata
Release files for integral-client-legacy 2.0.2
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 | |
|---|---|---|---|---|
| integral-client-legacy-2.0.2.tar.gz | 6.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| integral_client_legacy-2.0.2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 12.4 kB
Release files / integral-client-legacy-2.0.2.tar.gz
| Download URL | integral-client-legacy-2.0.2.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ad38b01f24b7e032f08c349c0927ffd36d95aeac422e99be1a86c4970ae1982
|
|
BLAKE2b-256 checksum How to use checksums |
98d347a4c7d9fffb82c9d26bf3ad93362ea96d35cf5cf77c898f35fe67cfefe5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / integral_client_legacy-2.0.2-py2.py3-none-any.whl
| Download URL | integral_client_legacy-2.0.2-py2.py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
3b5fc2c2113bd02fee64b0a36387b7e9dfc16bce55a89e0a3e83540d291e918a
|
|
BLAKE2b-256 checksum How to use checksums |
5d375a4cdcbce985d0ae1442eb408608f0b594000c1a62050486451688605070
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for integral-client-legacy 2.0.2
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.