1 maintainer
Metadata
1 maintainer
Release files for shedding-py 1.0.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 | |
|---|---|---|---|---|
| shedding_py-1.0.0.tar.gz | 5.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| shedding_py-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.6 kB
Release files / shedding_py-1.0.0.tar.gz
| Download URL | shedding_py-1.0.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2779291c50fa4fc7a7fd671771e8ae82df925df278bc8a680d7ac520bd4f8186
|
|
BLAKE2b-256 checksum How to use checksums |
5732be79016bcf6a9320c81daf0a34c0914efb78487ccd8e0336dd39ea367996
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.11.2 Linux/6.2.0-20-generic
|
Release files / shedding_py-1.0.0-py3-none-any.whl
| Download URL | shedding_py-1.0.0-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3cc6757360cc88bf27d2731ea7063267f233dd06761e20bf056ada95f52d6a60
|
|
BLAKE2b-256 checksum How to use checksums |
b75046c52b42a1ae8edafec36540409e743cb65db1a23fcb26528a0058ba8209
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.2 CPython/3.11.2 Linux/6.2.0-20-generic
|
Security for shedding-py 1.0.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.
