Metadata
1 maintainer
Release files for awesome-py-utils 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 | |
|---|---|---|---|---|
| awesome_py_utils-0.0.1.tar.gz | 2.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awesome_py_utils-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.9 kB
Release files / awesome_py_utils-0.0.1.tar.gz
| Download URL | awesome_py_utils-0.0.1.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec1946876f4457806939e909521ebf68dc29985c0adfd2146cd5a19d6e37bbc4
|
|
BLAKE2b-256 checksum How to use checksums |
7ec142612fbcf76246eeddd475a0aeb52df63a377a7040d147bc02439556208c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / awesome_py_utils-0.0.1-py3-none-any.whl
| Download URL | awesome_py_utils-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
405d063653ab09c68c131e099eb1bf0dfe804d13a79113b0a43d4b2676227da1
|
|
BLAKE2b-256 checksum How to use checksums |
78a8b7a0f618a9c6576767db04a2eb54caf26180def3dc0ddfe3b84c042c59e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for awesome-py-utils 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.
