My first Python package with a slightly longer description
Metadata
Release files for my-random-package 0.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 | |
|---|---|---|---|---|
| my-random-package-0.0.1.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| my_random_package-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.1 kB
Release files / my-random-package-0.0.1.tar.gz
| Download URL | my-random-package-0.0.1.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60f582f16c90279b330a99ea3cdf6a6b510b3e8feffb29fc4bbbd92e50a3702a
|
|
BLAKE2b-256 checksum How to use checksums |
b9a4ce291d2d75552133d99b14d0887de46e103f327c886a243cec864d727947
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Release files / my_random_package-0.0.1-py3-none-any.whl
| Download URL | my_random_package-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a90136398d7077016d5e65750ed4d4043b0f285af0d70e45da92cf826a04ef01
|
|
BLAKE2b-256 checksum How to use checksums |
036f306699128d2de31852f481d88d8d778af7772c09f4f38d874113b49ce653
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for my-random-package 0.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.