ICAT+ RESTful API with Swagger
Metadata
Release files for icat-plus-client 5.7.1
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 | |
|---|---|---|---|---|
| icat_plus_client-5.7.1.tar.gz | 152.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| icat_plus_client-5.7.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 446.8 kB
Release files / icat_plus_client-5.7.1.tar.gz
| Download URL | icat_plus_client-5.7.1.tar.gz |
|---|---|
| Size | 152.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f261b90de00cee7a337908698cfa42e8b66b83cbc750370c76f4373da7dd7089
|
|
BLAKE2b-256 checksum How to use checksums |
2582da039c50e5092bdd03f4835d1b641b1305b68cb9ebe4cb645f7f3ac907a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.22
|
Release files / icat_plus_client-5.7.1-py3-none-any.whl
| Download URL | icat_plus_client-5.7.1-py3-none-any.whl |
|---|---|
| Size | 294.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6359ca517047504285f81b08c336e641d328393c9a6f558623419b6e84bdb81e
|
|
BLAKE2b-256 checksum How to use checksums |
34bb1f420245638c623d06a4dae73997a651cde2c7a6de1fe09ddc49fe9ab76b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.22
|
Security for icat-plus-client 5.7.1
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.