The author of this package has not provided a project description
Metadata
Release files for rone 0.1.0
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 | |
|---|---|---|---|---|
| rone-0.1.0.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rone-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.2 kB
Release files / rone-0.1.0.tar.gz
| Download URL | rone-0.1.0.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80b7f3de423fa923288815dbc615b94b7697b096fcf5c52fc14ca9227fa29e8a
|
|
BLAKE2b-256 checksum How to use checksums |
f973db59f8202d2b48ab302f38c85cc0d801eda4c28297d10dcf508a9d193883
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Release files / rone-0.1.0-py3-none-any.whl
| Download URL | rone-0.1.0-py3-none-any.whl |
|---|---|
| Size | 959 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cb71f8f789d50648a31bbeb69a535b1e34b5748300e4f8291db9af5c27234a24
|
|
BLAKE2b-256 checksum How to use checksums |
23b4223263dffe3426d2c4f7049e9fa6835740ff9a15d92779443f7a25dd6cf8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for rone 0.1.0
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.