The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for coral-api 2.5.0
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 | |
|---|---|---|---|---|
| coral-api-2.5.0.tar.gz | 5.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| coral_api-2.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.3 MB
Release files / coral-api-2.5.0.tar.gz
| Download URL | coral-api-2.5.0.tar.gz |
|---|---|
| Size | 5.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7aa967bca84324cb4cda7a443f86a65156ced4a70ee9d4d65a93fe28d8fbfe42
|
|
BLAKE2b-256 checksum How to use checksums |
19027ace6d4ee3b115aa1faf9dea720359e86c1eab9c8dc55ec1fa67fb3faeda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Release files / coral_api-2.5.0-py3-none-any.whl
| Download URL | coral_api-2.5.0-py3-none-any.whl |
|---|---|
| Size | 5.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
579c8c774e6e2d951fc41d97f7755be932e5f8a1fd60c5e67f202d3648489e57
|
|
BLAKE2b-256 checksum How to use checksums |
3c3c049370df5b88b8a71b1bd3ed540f1a8dc767da9653256fcbb9beb03a2d39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Security for coral-api 2.5.0
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.
