upseeker
InsideOpt Seeker UP Linux Distribution
Credits
This package was created with Cookiecutter.
1 maintainer
Metadata
1 maintainer
Release files for upseeker 0.0.10
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 | |
|---|---|---|---|---|
| upseeker-0.0.10.tar.gz | 18.6 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| upseeker-0.0.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.9 MB
Release files / upseeker-0.0.10.tar.gz
| Download URL | upseeker-0.0.10.tar.gz |
|---|---|
| Size | 18.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c39185f3b50449384e95baf7a0a36e59bda12ec01d90866a509e65f47223cf20
|
|
BLAKE2b-256 checksum How to use checksums |
bb46f91298d6fa7454b14ca2e29172e0c014d58524f9d7512d0111ec4eb976dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Release files / upseeker-0.0.10-py3-none-any.whl
| Download URL | upseeker-0.0.10-py3-none-any.whl |
|---|---|
| Size | 21.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
137da774ef3065aadcbe241b8ab8bf4b7f1f9876461857b292c63971204923c4
|
|
BLAKE2b-256 checksum How to use checksums |
07b1f79cefb3eab059b0a6abe15602a4f9e25f43e3b970d511f8ddcb2d6cd3bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Security for upseeker 0.0.10
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.
