InsideOpt Seeker GEAS
Credits
This package was created with Cookiecutter.
Metadata
Release files for geasseeker 0.0.3
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 | |
|---|---|---|---|---|
| geasseeker-0.0.3.tar.gz | 46.9 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| geasseeker-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 93.0 MB
Release files / geasseeker-0.0.3.tar.gz
| Download URL | geasseeker-0.0.3.tar.gz |
|---|---|
| Size | 46.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ddf08423129e3157c6618d66aef19611fbdf8480fe2b322470085fed7341f4cc
|
|
BLAKE2b-256 checksum How to use checksums |
4d4c03f0939aa9d50364dc30a876fceb4c7e485ae8f9c1722323abb20657a200
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / geasseeker-0.0.3-py3-none-any.whl
| Download URL | geasseeker-0.0.3-py3-none-any.whl |
|---|---|
| Size | 46.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
692de59fe37f0faf6a3e895adab0f84f56e9eb28627e99a7dd7c27087d4c5c35
|
|
BLAKE2b-256 checksum How to use checksums |
ca540feb17c7d7e0b0742a5892013bc00c0b2a4074412ab3c776add1516abbe9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for geasseeker 0.0.3
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.