The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for sparsesketch 0.1.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 | |
|---|---|---|---|---|
| sparsesketch-0.1.0.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sparsesketch-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.7 kB
Release files / sparsesketch-0.1.0.tar.gz
| Download URL | sparsesketch-0.1.0.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a399b6c60e63d928b0944e39188a7a9b69bd13cfd52e2984cb9e117bf1c01a7a
|
|
BLAKE2b-256 checksum How to use checksums |
f6e0a204ddb0cb9d12eb05131143fb39fb931a8a26fdc319ec2483e02759d379
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.17
|
Release files / sparsesketch-0.1.0-py3-none-any.whl
| Download URL | sparsesketch-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
16db81df54161e4fafd1d706a7df40fa6b4e97b9cf356d1a45674e0f38a75bff
|
|
BLAKE2b-256 checksum How to use checksums |
61a35c9fb2bbf332c29adfd32da645e5d01c47db9597f1858111206646f0239b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.17
|
Security for sparsesketch 0.1.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.
