coming soon
2 maintainers
Metadata
2 maintainers
Release files for scigeo 0.0.15
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 | |
|---|---|---|---|---|
| scigeo-0.0.15.tar.gz | 11.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scigeo-0.0.15-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.7 kB
Release files / scigeo-0.0.15.tar.gz
| Download URL | scigeo-0.0.15.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
453a33d5528f89aee1868eda01deaf72d5f9c0010e1cb83c4aa9cf926bc1278b
|
|
BLAKE2b-256 checksum How to use checksums |
624566878e93359d3b1981bf18bab59348cb92b2bb3fd00116ea428cfb0e6306
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.3
|
Release files / scigeo-0.0.15-py3-none-any.whl
| Download URL | scigeo-0.0.15-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92ace5282ab207261c33cf373a76db01882be6f2650c3425460e5e16ea69e053
|
|
BLAKE2b-256 checksum How to use checksums |
fd3d9a8f6a017182c63f234fb8617bf981e8a9d21787d567e9b4d5472778fc09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.3
|
Security for scigeo 0.0.15
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.
