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