Render client for swiper.
Metadata
Release files for render-swiper 0.6.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 | |
|---|---|---|---|---|
| render_swiper-0.6.0.tar.gz | 194.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| render_swiper-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 400.6 kB
Release files / render_swiper-0.6.0.tar.gz
| Download URL | render_swiper-0.6.0.tar.gz |
|---|---|
| Size | 194.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67f1295bd043db462626b312d6d18b79f9abd20e4eeeb602e436caa9d8681679
|
|
BLAKE2b-256 checksum How to use checksums |
a7e4c21e8f9bf573efc8b10b6cdd61a7bec87993d4efe9a7de25777871a7aaf4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.11.2 Darwin/23.5.0
|
Release files / render_swiper-0.6.0-py3-none-any.whl
| Download URL | render_swiper-0.6.0-py3-none-any.whl |
|---|---|
| Size | 205.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
32650533bca5dd3d1112a6994e1f01bdf808f55680700fa7ef7434aac2eada83
|
|
BLAKE2b-256 checksum How to use checksums |
d98734715dd170a97737554afa736ba5b82374840698a77f15efba271565b74a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.11.2 Darwin/23.5.0
|
Security for render-swiper 0.6.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.