The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for skcan-compare 0.0.3
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 | |
|---|---|---|---|---|
| skcan-compare-0.0.3.tar.gz | 11.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| skcan_compare-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.0 kB
Release files / skcan-compare-0.0.3.tar.gz
| Download URL | skcan-compare-0.0.3.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1bf39e1144271f4e8e71acc26a583d9e7fa9305482b0093d0b1f115186f4bde5
|
|
BLAKE2b-256 checksum How to use checksums |
84b793c4458bb828ca203941f337fc2cc95af84b4084b08cec15b6557c022093
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / skcan_compare-0.0.3-py3-none-any.whl
| Download URL | skcan_compare-0.0.3-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dcac89d95cf46d26786091b5481c123be853671120c48e3f699f9126c41e41a4
|
|
BLAKE2b-256 checksum How to use checksums |
fd1695fc870ac3647bb00631d50f4c6b0a17521d31f7bd461c97ac15f7efe352
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for skcan-compare 0.0.3
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.
