The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for usbreq 0.2.1
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 | |
|---|---|---|---|---|
| usbreq-0.2.1.tar.gz | 7.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| usbreq-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.2 kB
Release files / usbreq-0.2.1.tar.gz
| Download URL | usbreq-0.2.1.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fbf7f3405cf4e5b06efb232ea1446cc1d09e64bb66b844f9fe104aa980760c1e
|
|
BLAKE2b-256 checksum How to use checksums |
8612db67417c1cfebbaea6bbde7e6a91464ff181974b9dbee52f6eabe844cbdb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Release files / usbreq-0.2.1-py3-none-any.whl
| Download URL | usbreq-0.2.1-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1070756c68195e9704956c05be7a56143a9565534b7ec962e5badc808decc994
|
|
BLAKE2b-256 checksum How to use checksums |
7116120b4ae5f79089ec744ccdeb688e4c2de438046f9767b3a374da5248c39f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for usbreq 0.2.1
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.
