Metadata
Release files for rusn 1.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 | |
|---|---|---|---|---|
| rusn-1.0.1.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rusn-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.9 kB
Release files / rusn-1.0.1.tar.gz
| Download URL | rusn-1.0.1.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c10085ec812c43f05aed51b1173c7cd292890f98c03e9e390f2f2a5a692ad9e
|
|
BLAKE2b-256 checksum How to use checksums |
a204ff16e90559dccfa41dfe7a9b76d082a35e48f436acfb9e275556cf582683
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.2
|
Release files / rusn-1.0.1-py3-none-any.whl
| Download URL | rusn-1.0.1-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1055f78489a481863d99a0954c6be83a23e87c19b0341fd90d2619eec976cb7a
|
|
BLAKE2b-256 checksum How to use checksums |
16fba43b5b47d08c26fcc516b9736094876d64824112cc66b5869d8fa460b6d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.2
|
Security for rusn 1.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.