The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for riverbend 1.1.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 | |
|---|---|---|---|---|
| riverbend-1.1.1.tar.gz | 984.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| riverbend-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 MB
Release files / riverbend-1.1.1.tar.gz
| Download URL | riverbend-1.1.1.tar.gz |
|---|---|
| Size | 984.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd9f7d9fbdc2f4a49e0d11a110c33ea0c2025bdb4b3d72a570c9832167110a01
|
|
BLAKE2b-256 checksum How to use checksums |
5c4f7576ba90ca4baa74c9eaeab042b941b4aeef5daee74ed2c57748a9a42671
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / riverbend-1.1.1-py3-none-any.whl
| Download URL | riverbend-1.1.1-py3-none-any.whl |
|---|---|
| Size | 994.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e4732ae097866543d62be08763d92a20c1ec401763348b6ff9a18babf9d8abff
|
|
BLAKE2b-256 checksum How to use checksums |
14a5a32d23d0bc1518ba1394559bc44ffff9ed60b1a63deda4847cd219ae17be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for riverbend 1.1.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.
