The author of this package has not provided a project description
Metadata
Release files for rues 0.1.1.3
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 | |
|---|---|---|---|---|
| rues-0.1.1.3.tar.gz | 22.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rues-0.1.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.0 kB
Release files / rues-0.1.1.3.tar.gz
| Download URL | rues-0.1.1.3.tar.gz |
|---|---|
| Size | 22.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ae86fb679f026a0bd7a7b121344770179859848271569c1ced31601764a46ee
|
|
BLAKE2b-256 checksum How to use checksums |
4d9133c1fda30cb8e6f6452a94f9d15b05bc541fd2cdb16e3a3e1327164a981a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.2 CPython/3.8.3 Linux/5.3.0-53-generic
|
Release files / rues-0.1.1.3-py3-none-any.whl
| Download URL | rues-0.1.1.3-py3-none-any.whl |
|---|---|
| Size | 28.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f9a6d2ed69b38f4ecc0772ae0fd9c5bf00c07de1137e901a5c588af9c30e579
|
|
BLAKE2b-256 checksum How to use checksums |
179acaed3f483dc24f6593ccf35ca556505505ec93476ea1e6b8f95d4bebe8a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.2 CPython/3.8.3 Linux/5.3.0-53-generic
|
Security for rues 0.1.1.3
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.