Metadata
Release files for OpenGeodeWeb-Viewer 1.35.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.35.0.tar.gz | 67.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opengeodeweb_viewer-1.35.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 239.8 kB
Release files / opengeodeweb_viewer-1.35.0.tar.gz
| Download URL | opengeodeweb_viewer-1.35.0.tar.gz |
|---|---|
| Size | 67.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21150b50d3cea63dc169da8afd718b9b09e14979208c09b1aa3533b2718cffbe
|
|
BLAKE2b-256 checksum How to use checksums |
92be4ee7540bfb26a01950575cdaace9d05161f03f0edf91b352f85b237e27cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.14.8
|
Release files / opengeodeweb_viewer-1.35.0-py3-none-any.whl
| Download URL | opengeodeweb_viewer-1.35.0-py3-none-any.whl |
|---|---|
| Size | 172.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbc716c2bcba46ed25f3a028f1a82ccb1e9b7874359eca658617876be171345e
|
|
BLAKE2b-256 checksum How to use checksums |
5fb990a9774f076a82e8f6da85d3e895241629457c3a3f85033877fae2727568
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.14.8
|
Security for OpenGeodeWeb-Viewer 1.35.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.