Metadata
Release files for OpenGeodeWeb-Viewer 1.34.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 | |
|---|---|---|---|---|
| opengeodeweb_viewer-1.34.0.tar.gz | 60.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opengeodeweb_viewer-1.34.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 208.1 kB
Release files / opengeodeweb_viewer-1.34.0.tar.gz
| Download URL | opengeodeweb_viewer-1.34.0.tar.gz |
|---|---|
| Size | 60.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0586027e49f1801325b57abeda09d2bfece1bdd2f4732ef9be6a74fd0b69c328
|
|
BLAKE2b-256 checksum How to use checksums |
65a21acd1069b7960f6d302608aee61174a24b278fb003a2b2022535f6d1a046
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.15
|
Release files / opengeodeweb_viewer-1.34.0-py3-none-any.whl
| Download URL | opengeodeweb_viewer-1.34.0-py3-none-any.whl |
|---|---|
| Size | 147.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
275bc3c6cff02a413a9489e101c77e057a6a47bf13a565ad3ee0eb9c55a54d2b
|
|
BLAKE2b-256 checksum How to use checksums |
7be3e733c58ed56a56f98f94b5de638d646f7c893125bc62a5afe3592eca9b01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.15
|
Security for OpenGeodeWeb-Viewer 1.34.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.