The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for nu-lpw-ec 0.0.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 | |
|---|---|---|---|---|
| nu_lpw_ec-0.0.1.tar.gz | 9.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nu_lpw_ec-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.6 kB
Release files / nu_lpw_ec-0.0.1.tar.gz
| Download URL | nu_lpw_ec-0.0.1.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec6a94422a73ae8fd54adcfb2bc432d4c37a4d3a6cff96665aa594afe24f2610
|
|
BLAKE2b-256 checksum How to use checksums |
e4eec5094ae49b6f3d5c832618dad3207b1ccf087da1e6b4c30197ea2ee2b0cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / nu_lpw_ec-0.0.1-py3-none-any.whl
| Download URL | nu_lpw_ec-0.0.1-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a16f05c578765234dcd1d396665df0098696dd42cfb91db02ec51c2500b773a
|
|
BLAKE2b-256 checksum How to use checksums |
266f9148a73416d37a61e2720bd74e1d5a2fa3a52bb3b59a1d1eb0cc18e44f48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for nu-lpw-ec 0.0.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.
