A Python wrapper for the Binance C2C (Customer-to-Customer) SAPI.
Metadata
Release files for cs-binance-c2c-sapi 0.0.11
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 | |
|---|---|---|---|---|
| cs-binance-c2c-sapi-0.0.11.tar.gz | 4.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cs_binance_c2c_sapi-0.0.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.3 kB
Release files / cs-binance-c2c-sapi-0.0.11.tar.gz
| Download URL | cs-binance-c2c-sapi-0.0.11.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70dcebc3f42827730ab6b2994fb2f5ebcffb7354681039786491eebe359fa31f
|
|
BLAKE2b-256 checksum How to use checksums |
253458024f547e2a810456badb9d7570c0a5a804c308b017c0510cab06facb76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Release files / cs_binance_c2c_sapi-0.0.11-py3-none-any.whl
| Download URL | cs_binance_c2c_sapi-0.0.11-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
adf604100e5e4431641caef3e96ec247d0515ba30e2b520a77d4ebb360e01cdb
|
|
BLAKE2b-256 checksum How to use checksums |
e3bc95ad29efe90ed98a3bf796092ee24a40eaaefbe6798e0db105bc947c7ca2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Security for cs-binance-c2c-sapi 0.0.11
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.