The author of this package has not provided a project description
Metadata
Release files for geoconformal 0.3.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 | |
|---|---|---|---|---|
| geoconformal-0.3.0.tar.gz | 30.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| geoconformal-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.0 kB
Release files / geoconformal-0.3.0.tar.gz
| Download URL | geoconformal-0.3.0.tar.gz |
|---|---|
| Size | 30.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75345a80122f346a95fcb247771e31f42ffaf3ce515449fb061e57a5b640e8bb
|
|
BLAKE2b-256 checksum How to use checksums |
792803ed43bde46739b18e3431383b6a224cbf57a741b40995d523477a7d8c79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / geoconformal-0.3.0-py3-none-any.whl
| Download URL | geoconformal-0.3.0-py3-none-any.whl |
|---|---|
| Size | 24.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8da1e32f1fbd00bb957c1bbfe3a2d62614d9889e25212545d40ab42454b40cdc
|
|
BLAKE2b-256 checksum How to use checksums |
602e9a22ede0fafa13a7f2ccb054fe0b2672cb06357bbd141af7b77bed6bb15e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for geoconformal 0.3.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.