The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aew-api 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 | |
|---|---|---|---|---|
| aew_api-0.1.0.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aew_api-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 kB
Release files / aew_api-0.1.0.tar.gz
| Download URL | aew_api-0.1.0.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
64670c3dbf68f46dd5839e448c7a830ef7eaa6bf12b40b1c8e0b1dfd5866c96e
|
|
BLAKE2b-256 checksum How to use checksums |
43e15ef3778aa97599b3bf278eaf8355abd1c28850cfead161b4fe1eb33b16d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.1
|
Release files / aew_api-0.1.0-py3-none-any.whl
| Download URL | aew_api-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
024c0b51ebedc4991484f6f76030008116d716be9c3a80ed3e4065073977cb23
|
|
BLAKE2b-256 checksum How to use checksums |
7ba75ffed9fd2b6540d5e65252de6003d43e08153d0c4bd6ae1ae0c3d74b6136
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.1
|
Security for aew-api 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.
