ICAT+ RESTful API with Swagger
Metadata
Release files for icat-plus-client 5.7.3
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.3.tar.gz | 152.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| icat_plus_client-5.7.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 446.7 kB
Release files / icat_plus_client-5.7.3.tar.gz
| Download URL | icat_plus_client-5.7.3.tar.gz |
|---|---|
| Size | 152.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcf93f3427083d32c8c32f47d92282bfcffc16dc8633258b660c189cc23c1ff9
|
|
BLAKE2b-256 checksum How to use checksums |
229edcfb35d35b68c0b70b9900b4d697574810931b5db1db5f1876660c07678e
|
| 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.3-py3-none-any.whl
| Download URL | icat_plus_client-5.7.3-py3-none-any.whl |
|---|---|
| Size | 294.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41f6182c808a87a31894120913c8efeed45435b174df96d8265eccde8b90c817
|
|
BLAKE2b-256 checksum How to use checksums |
0dd21e4a70f2a42d201477fa444b74b55d6a27470cb3f025def76de824cf6299
|
| 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.3
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.