InsideOpt Seeker CQM Windows Distribution
Credits
This package was created with Cookiecutter.
Metadata
Release files for cqmseeker 0.0.5
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 | |
|---|---|---|---|---|
| cqmseeker-0.0.5.tar.gz | 6.2 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cqmseeker-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.7 MB
Release files / cqmseeker-0.0.5.tar.gz
| Download URL | cqmseeker-0.0.5.tar.gz |
|---|---|
| Size | 6.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75bee282e8210d8c44f86b80f484f597f33360c4ac1a2a2a8bba7aca5069fea1
|
|
BLAKE2b-256 checksum How to use checksums |
886b614a44e31f2dab199720df868cd33f2e72dd310dd1bb2e9acfb3c7922e81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / cqmseeker-0.0.5-py3-none-any.whl
| Download URL | cqmseeker-0.0.5-py3-none-any.whl |
|---|---|
| Size | 5.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77de5e55a6bdd7999d0119f40359baecf7d2fa08d2a98e2f41387f333f18af2c
|
|
BLAKE2b-256 checksum How to use checksums |
f2cd07b0904dfff9a0f02ef36eba8b76bb4d0fd08923f1611ba1e28d1955b1d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for cqmseeker 0.0.5
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.