The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for a4a-sdk 0.4.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 | |
|---|---|---|---|---|
| a4a_sdk-0.4.0.tar.gz | 485.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| a4a_sdk-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 670.1 kB
Release files / a4a_sdk-0.4.0.tar.gz
| Download URL | a4a_sdk-0.4.0.tar.gz |
|---|---|
| Size | 485.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f474ab78426358449b001b115322c5c2e8b83eef347368ecf010b91278c950c8
|
|
BLAKE2b-256 checksum How to use checksums |
11e377b85f1cd843557431e08b03923edd55f321e7d3a3625233e3c0a7a0d801
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Release files / a4a_sdk-0.4.0-py3-none-any.whl
| Download URL | a4a_sdk-0.4.0-py3-none-any.whl |
|---|---|
| Size | 184.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
716c52670ce61ae31a9c7d0f1dcef01e3c41e1a9591cb4a0d5128d2fcbce277b
|
|
BLAKE2b-256 checksum How to use checksums |
e817e838843ad7a0c396794e8e019a09c4b5343348cf9836745744b1d5cac289
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Security for a4a-sdk 0.4.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.
