1 maintainer
Metadata
1 maintainer
Release files for peer-lilo 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 | |
|---|---|---|---|---|
| peer-lilo-0.0.1.tar.gz | 31.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| peer_lilo-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.1 kB
Release files / peer-lilo-0.0.1.tar.gz
| Download URL | peer-lilo-0.0.1.tar.gz |
|---|---|
| Size | 31.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e436d41f60fadabdf665f18275550965101f4229c291c953be66fc3ea578155
|
|
BLAKE2b-256 checksum How to use checksums |
d6494d3a01a20ef5d6ea830fc255185d59d986a31ce9658b88e5f17fb05542b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / peer_lilo-0.0.1-py3-none-any.whl
| Download URL | peer_lilo-0.0.1-py3-none-any.whl |
|---|---|
| Size | 37.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b1760986c749eb40232f280e056814bbe8a27866ff000c455a89a46462f722e
|
|
BLAKE2b-256 checksum How to use checksums |
ba4972c93569f408704b51d8c7665884d0d0ec6d762415a35a892e2fe3cb5f6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for peer-lilo 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.
