The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for lapatic-mpy 0.1.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 | |
|---|---|---|---|---|
| lapatic_mpy-0.1.0.tar.gz | 7.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lapatic_mpy-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.5 kB
Release files / lapatic_mpy-0.1.0.tar.gz
| Download URL | lapatic_mpy-0.1.0.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d85b4baf92e3eacfc27e1d475c9d218a26ba95254ae26c5baedf2d43f5620dac
|
|
BLAKE2b-256 checksum How to use checksums |
ad9478dc11f47d483111716e7a687ba5d6d678b150ac5ece65a2ce0d0843bf0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / lapatic_mpy-0.1.0-py3-none-any.whl
| Download URL | lapatic_mpy-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7773181f214fad2aa4283b9f2e5034d3d1bf3c03dd368eefb60d8ca64b4e3071
|
|
BLAKE2b-256 checksum How to use checksums |
c6b3f132f33258d73bf06287d2c8bde409e3b9c3e4ffa4469a1f0a8cbcaf5750
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for lapatic-mpy 0.1.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.
