1 maintainer
Metadata
1 maintainer
Release files for rio-xpw 0.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 | |
|---|---|---|---|---|
| rio_xpw-0.1.tar.gz | 9.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rio_xpw-0.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 20.1 kB
Release files / rio_xpw-0.1.tar.gz
| Download URL | rio_xpw-0.1.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46e9a1908198f2d7883c4f950f989db78e02e24a2ebd7ad1253fc0deb4b29ba3
|
|
BLAKE2b-256 checksum How to use checksums |
32ea33ff8a90d14c453a9df8e1c16d7bd38bde12752a6edf0628734719f12c6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / rio_xpw-0.1-py2.py3-none-any.whl
| Download URL | rio_xpw-0.1-py2.py3-none-any.whl |
|---|---|
| Size | 10.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
374cdf870afb4121d54c2afbe5d721234b3e8a6ac2d126a05a3a8da5ea9c516b
|
|
BLAKE2b-256 checksum How to use checksums |
78003ed0500537f8907ef0f4e2e962f9bee2fda08f8310fe9bbbe82221a84680
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for rio-xpw 0.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.
