1 maintainer
Metadata
1 maintainer
Release files for rpi-lcd-i2c-animations 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 | |
|---|---|---|---|---|
| rpi_lcd_i2c_animations-0.1.0.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rpi_lcd_i2c_animations-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.5 kB
Release files / rpi_lcd_i2c_animations-0.1.0.tar.gz
| Download URL | rpi_lcd_i2c_animations-0.1.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
49681d433058558769319d5ed7e2049ffa4f9a69b26c8e69aa2307ef2075315b
|
|
BLAKE2b-256 checksum How to use checksums |
43e1b4fac9c2531cdf979b882cb626da3574c02941bafa29836bb8f18a606d30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Release files / rpi_lcd_i2c_animations-0.1.0-py3-none-any.whl
| Download URL | rpi_lcd_i2c_animations-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76d9879e8dc7f0846e60d7a2393733ebd8b2f83c0f7e8e1cd3897200544ec145
|
|
BLAKE2b-256 checksum How to use checksums |
79cad9c95aa0d6ea1e5ec781e8e1fea114aa2a6b7020f737dbd605ef313f9da4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Security for rpi-lcd-i2c-animations 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.
