The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for lilo.mdof 0.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 | |
|---|---|---|---|---|
| lilo_mdof-0.0.0.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lilo.mdof-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / lilo_mdof-0.0.0.tar.gz
| Download URL | lilo_mdof-0.0.0.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52a9b271d6e90b80be21af0c25a947dcaa7d87a5a11b15c37419a838b2fcdbc5
|
|
BLAKE2b-256 checksum How to use checksums |
679a59d024c62b89b2aac171829228daae77d079f7ce73b852e987afd5e1e047
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Release files / lilo.mdof-0.0.0-py3-none-any.whl
| Download URL | lilo.mdof-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a67e6741fba199e0cef75b860fcc5c3504e749151820ada46b1feccd8f9055c
|
|
BLAKE2b-256 checksum How to use checksums |
07f65271f2f485438e8ae410a838b99cd97ea9370048f56d18ca57974ed1db3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Security for lilo.mdof 0.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.
