Metadata
1 maintainer
Release files for aeza 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 | |
|---|---|---|---|---|
| aeza-0.1.0.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aeza-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.1 kB
Release files / aeza-0.1.0.tar.gz
| Download URL | aeza-0.1.0.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60701e9db5da059aa3ce4a9feb86d12d8b28964516f0f07d4cd2f4b228d4f173
|
|
BLAKE2b-256 checksum How to use checksums |
0fa8dc531261d073417f64a6cfd02d1f1f13d18cf7fc940a74a6c34a44bcff5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.2 CPython/3.11.2 Linux/6.2.9-200.fc37.x86_64
|
Release files / aeza-0.1.0-py3-none-any.whl
| Download URL | aeza-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eeb11b2bb7b04dc2b7421edaa04adefaf1331cda36958f8834285cb9b0c9e897
|
|
BLAKE2b-256 checksum How to use checksums |
23dbcc3a117a5b2eb8b649c0ea9ea5dfd6ae22e1bc6eed59bb8b31dcf5a5c660
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.2 CPython/3.11.2 Linux/6.2.9-200.fc37.x86_64
|
Security for aeza 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.
