1 maintainer
Metadata
1 maintainer
Release files for xrp-usb-controller 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 | |
|---|---|---|---|---|
| xrp_usb_controller-0.1.0.tar.gz | 42.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xrp_usb_controller-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 72.6 kB
Release files / xrp_usb_controller-0.1.0.tar.gz
| Download URL | xrp_usb_controller-0.1.0.tar.gz |
|---|---|
| Size | 42.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d7be7f68108575e1cbf7413cccf080b1a5cc97b863446065e31f8ead710a9d2
|
|
BLAKE2b-256 checksum How to use checksums |
d5fa060b01cdb78cec1d6b7c489096f71b3d95ce7bd92e1aa0875500f147ec09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / xrp_usb_controller-0.1.0-py3-none-any.whl
| Download URL | xrp_usb_controller-0.1.0-py3-none-any.whl |
|---|---|
| Size | 30.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f309b9cfdfac6dd486b5d8ffb98feea8d6380cecc2afe2d206296932421e5bc6
|
|
BLAKE2b-256 checksum How to use checksums |
8180b9392a61cf04b505bcca6f5a3db90ae67ce85819b61ba9300d2f93497086
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for xrp-usb-controller 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.
