1 maintainer
Metadata
1 maintainer
Release files for aai-python-codes 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 | |
|---|---|---|---|---|
| aai_python_codes-0.1.0.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aai_python_codes-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.0 kB
Release files / aai_python_codes-0.1.0.tar.gz
| Download URL | aai_python_codes-0.1.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b06a8728cff2de143d10388762dd66b572a1c897df968d478c49e8103f1bb79
|
|
BLAKE2b-256 checksum How to use checksums |
40a960df0c8119d6740867449686d61188f6a25c2fce4545f580d7f28b20b347
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.5
|
Release files / aai_python_codes-0.1.0-py3-none-any.whl
| Download URL | aai_python_codes-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
afcb23032e4a19ce6be90f55235596feacd05f5b7765914e47e49bf5e31c151b
|
|
BLAKE2b-256 checksum How to use checksums |
644cd55d6c35be2750409e83e95b2fe6dce4a851601d7a22260a9d81e9b5c5a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.5
|
Security for aai-python-codes 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.
