The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for covsight 0.2.0
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 | |
|---|---|---|---|---|
| covsight-0.2.0.tar.gz | 159.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| covsight-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 241.5 kB
Release files / covsight-0.2.0.tar.gz
| Download URL | covsight-0.2.0.tar.gz |
|---|---|
| Size | 159.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e1c723b234d5c54f8264f8f2a604ee6b7e4d9619a89fbef59c9065b3483e27e
|
|
BLAKE2b-256 checksum How to use checksums |
10a649968acb2bc7f2b6d3b4692802911e20cb1d3f89b8d0d0ff56a73ed5b4f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / covsight-0.2.0-py3-none-any.whl
| Download URL | covsight-0.2.0-py3-none-any.whl |
|---|---|
| Size | 82.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f101bed5e6028f4a78b45672590aa42bf802912a0b9e222acb5d63adc558026
|
|
BLAKE2b-256 checksum How to use checksums |
ee937c246d6e0be7d41ec4be32d555a22391f69a4e06cc1112a75a86ede0fe81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for covsight 0.2.0
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.
