Metadata
Release files for cloudguard-interfaces 1.0.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 | |
|---|---|---|---|---|
| cloudguard_interfaces-1.0.0.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cloudguard_interfaces-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.1 kB
Release files / cloudguard_interfaces-1.0.0.tar.gz
| Download URL | cloudguard_interfaces-1.0.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41f9c7847c0b1646f4c19d1d9ccc19afa890c285d37e2574e0055ca52ec56bd3
|
|
BLAKE2b-256 checksum How to use checksums |
c4114ebf94eb9dac410725c36b3545085c9a9a359ba4227ae2376a0e5b93e6ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.5 Linux/6.2.0-1011-azure
|
Release files / cloudguard_interfaces-1.0.0-py3-none-any.whl
| Download URL | cloudguard_interfaces-1.0.0-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cf68432e08cfd5b5de5284a113157fb9d4f911865366d532e04993311caaa10f
|
|
BLAKE2b-256 checksum How to use checksums |
d8f80d6bacc40a6915897211a3c05786d1e33d0d541217dad5bdb6817f34cda5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.5 Linux/6.2.0-1011-azure
|
Security for cloudguard-interfaces 1.0.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.