1 maintainer
Metadata
1 maintainer
Release files for aptos-python-sdk 0.0.1
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 | |
|---|---|---|---|---|
| aptos_python_sdk-0.0.1.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aptos_python_sdk-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.1 kB
Release files / aptos_python_sdk-0.0.1.tar.gz
| Download URL | aptos_python_sdk-0.0.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7165147596e76bca29fc6545f3bebef47a7a25ebace2b1060746286891a61ce
|
|
BLAKE2b-256 checksum How to use checksums |
8da452a0b7801fe03108086f734637b55331f4e49fa72274e8c9016b940e8361
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.11
|
Release files / aptos_python_sdk-0.0.1-py3-none-any.whl
| Download URL | aptos_python_sdk-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ec44442155f46705173d7078d35d2accdec4ff94415a8830532473e5734f9fc
|
|
BLAKE2b-256 checksum How to use checksums |
5fd2871d9018d0084e80f4a67897942c14eea320a1eb70d20a5805d6b233ad5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.11
|
Security for aptos-python-sdk 0.0.1
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.
