The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for libla 0.0.2
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 | |
|---|---|---|---|---|
| libla-0.0.2.tar.gz | 5.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| libla-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.0 kB
Release files / libla-0.0.2.tar.gz
| Download URL | libla-0.0.2.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed2a22dcbe083b03dd7468fe1bfc8ceb2c404f9250fc2138f10b0120149497ea
|
|
BLAKE2b-256 checksum How to use checksums |
118a223d02961938492efa0d705853b4857fe79b38535ada455bccafae001106
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.8.7 Darwin/20.2.0
|
Release files / libla-0.0.2-py3-none-any.whl
| Download URL | libla-0.0.2-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
47fff0de7de74c3e8c7a6122b88c273501bfa95714bbc3e1231fab233076667c
|
|
BLAKE2b-256 checksum How to use checksums |
bfa58165fa21a37ac0e81318a34a70b718590e8233e18d389c7317be2f04fdf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.8.7 Darwin/20.2.0
|
Security for libla 0.0.2
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.
