The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for lapatic-uie 0.1.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 | |
|---|---|---|---|---|
| lapatic_uie-0.1.1.tar.gz | 6.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lapatic_uie-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / lapatic_uie-0.1.1.tar.gz
| Download URL | lapatic_uie-0.1.1.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c00eef479ebbd219c68a0eccbc6513337c44c7567fc76d7d4bd6f727bce141d
|
|
BLAKE2b-256 checksum How to use checksums |
9d36e811ab08ff23ee5b072e3086c714da9d6a7301dc949f5c04bdc5c59efa6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / lapatic_uie-0.1.1-py3-none-any.whl
| Download URL | lapatic_uie-0.1.1-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
50ee408e1937ef19278f712bce9a5ab9aba4dc89b2926e3cbc22b3f1551f8eae
|
|
BLAKE2b-256 checksum How to use checksums |
7911d36771b9cacffead67d40267f7e44f661b499ebc464ffb635a7ff83c7410
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for lapatic-uie 0.1.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.
