The author of this package has not provided a project description
Metadata
Release files for aleva 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 | |
|---|---|---|---|---|
| aleva-0.1.0.tar.gz | 609 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aleva-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / aleva-0.1.0.tar.gz
| Download URL | aleva-0.1.0.tar.gz |
|---|---|
| Size | 609 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f1cd2da4121339e40c1e04afc08b6e47afc4dce9eb61a9303351fd8ff041691
|
|
BLAKE2b-256 checksum How to use checksums |
383e17218949623a84d1e29410d1b146f36ac8f594d1c2c00a9f06f010addc2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.2 CPython/3.10.12 Linux/5.15.0-135-generic
|
Release files / aleva-0.1.0-py3-none-any.whl
| Download URL | aleva-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
821ec4cb582b24478dd8ea20d48a1a3877a7ac81c28d9002d048b3f0cc486e41
|
|
BLAKE2b-256 checksum How to use checksums |
43116acef44438f24948db462e4b78da0e4255b6353a6e10ed526d04429427de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.2 CPython/3.10.12 Linux/5.15.0-135-generic
|
Security for aleva 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.