test-seeker
InsideOpt Seeker Demo Distribution
Credits
This package was created with Cookiecutter.
1 maintainer
Metadata
1 maintainer
Release files for seekerdemo 0.0.36
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 | |
|---|---|---|---|---|
| seekerdemo-0.0.36.tar.gz | 2.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seekerdemo-0.0.36-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.3 kB
Release files / seekerdemo-0.0.36.tar.gz
| Download URL | seekerdemo-0.0.36.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e394309dff4d6ff9f997c9e072ad3ff7245b30aaf185a363d34757affc6156e
|
|
BLAKE2b-256 checksum How to use checksums |
c91ea484ca8e82d65c5274c2213f1f5143de210e7925642c553c1ba68c388451
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / seekerdemo-0.0.36-py3-none-any.whl
| Download URL | seekerdemo-0.0.36-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c64f5bec76ef88830d1f5906a1efb1c4accd8cdb05121f2ced8f279993700e1f
|
|
BLAKE2b-256 checksum How to use checksums |
f0abb6f8ef6d0011d1c05352c40efdf2b83cedb708f0c024a486a917d216588d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for seekerdemo 0.0.36
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.
