The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for lpro-s 1.2.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 | |
|---|---|---|---|---|
| lpro_s-1.2.1.tar.gz | 465.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lpro_s-1.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 934.8 kB
Release files / lpro_s-1.2.1.tar.gz
| Download URL | lpro_s-1.2.1.tar.gz |
|---|---|
| Size | 465.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1abe7acbabd464f21cbce2bc2bdc482ad1612e548e7d094c2a940e59621a6451
|
|
BLAKE2b-256 checksum How to use checksums |
ae1549f2052c88d903f41105c10c2f52577a48c62bc048346af2319ae9f92c64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / lpro_s-1.2.1-py3-none-any.whl
| Download URL | lpro_s-1.2.1-py3-none-any.whl |
|---|---|
| Size | 469.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d3dd6e6ebc48d05ec782e8fbe366a3649bf17fefa4d407404e981cdefd03cffa
|
|
BLAKE2b-256 checksum How to use checksums |
e5627a384b916ba3a84df69e51d9735faf737b33af6f94753a1f390a7780af6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for lpro-s 1.2.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.
