The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for a4a-sdk 0.3.3
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.3.3.tar.gz | 485.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| a4a_sdk-0.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 670.0 kB
Release files / a4a_sdk-0.3.3.tar.gz
| Download URL | a4a_sdk-0.3.3.tar.gz |
|---|---|
| Size | 485.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee19e7f960eb6e308c2dcef53e8cd7ab6c01b3bf5f3f47a5335937bd68a5f5aa
|
|
BLAKE2b-256 checksum How to use checksums |
2d93b09a0a7d537c525d9634b96d0b2f449d8eaecd606a7b4827882e3957da00
|
| 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.3.3-py3-none-any.whl
| Download URL | a4a_sdk-0.3.3-py3-none-any.whl |
|---|---|
| Size | 184.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f72e3e0093447d3dd780711a6a2989d024eb71dbee59d786cec2b4d49d15428
|
|
BLAKE2b-256 checksum How to use checksums |
ca1bf1dc68a1ca306e1a4cecef1297a51f5e5b2163ce1c21b4fc96b28c6b3aba
|
| 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.3.3
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.
