ICAT+ RESTful API with Swagger
Metadata
Release files for icat-plus-client 5.7.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 | |
|---|---|---|---|---|
| icat_plus_client-5.7.2.tar.gz | 152.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| icat_plus_client-5.7.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 446.8 kB
Release files / icat_plus_client-5.7.2.tar.gz
| Download URL | icat_plus_client-5.7.2.tar.gz |
|---|---|
| Size | 152.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f5e155c0eac35a0640712394752174b99bffee0f758f02f3e066b9a6f64e5f6
|
|
BLAKE2b-256 checksum How to use checksums |
88f67026a689583b373b96b76356a8c720ba05ce4f60093c4d3ff4fbbf9d2946
|
| 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.2-py3-none-any.whl
| Download URL | icat_plus_client-5.7.2-py3-none-any.whl |
|---|---|
| Size | 294.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b8f4667ff8c22e8402deea26107236ba3e183d63e3beee34e79f302df889303
|
|
BLAKE2b-256 checksum How to use checksums |
52da17c2efb30f56945354d7c9db2ba229699ccd541f017d9fc61dd3e935d757
|
| 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.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.