The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aoalabcode 1.0.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 | |
|---|---|---|---|---|
| aoalabcode-1.0.0.tar.gz | 6.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aoalabcode-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.1 kB
Release files / aoalabcode-1.0.0.tar.gz
| Download URL | aoalabcode-1.0.0.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3aa397b74bbb4b1201f1e33a4a7fed278cd5ffd4708c78bd3886d1e9eb59f911
|
|
BLAKE2b-256 checksum How to use checksums |
17a25a1620db6ac2c95d633f0254183fb89b4806a3424cfc29743c0c5f979234
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / aoalabcode-1.0.0-py3-none-any.whl
| Download URL | aoalabcode-1.0.0-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c0c1ca96c5ccfc0ad894225857cee3b7fd0fc5fdb427538e79c30f069410eaa
|
|
BLAKE2b-256 checksum How to use checksums |
5a91662f4c49e0b93e950ea76a357cec39279cf10bce1034e63392578baf14b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for aoalabcode 1.0.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.
