Release files for edx-braze-client 1.1.4
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 | |
|---|---|---|---|---|
| edx_braze_client-1.1.4.tar.gz | 38.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| edx_braze_client-1.1.4-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 74.7 kB
Release files / edx_braze_client-1.1.4.tar.gz
| Download URL | edx_braze_client-1.1.4.tar.gz |
|---|---|
| Size | 38.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db2c170e30f2761dcde5918ba4828101aa06c5a4ad3829496b804250ee9f7e13
|
|
BLAKE2b-256 checksum How to use checksums |
b90d5bb2e78d2dffbb8241ad9295b1638f63118ca09eb65d97cef4eefea99c33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / edx_braze_client-1.1.4-py2.py3-none-any.whl
| Download URL | edx_braze_client-1.1.4-py2.py3-none-any.whl |
|---|---|
| Size | 36.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
140ef1a327a4ecf5c3e7b2ae09a48b2c22ce98c3b1a14c575d592de109d072ec
|
|
BLAKE2b-256 checksum How to use checksums |
d3a3056eb8a4fbaa94ee6bc957c80264ce7b1dd985f5a6f5b5514eba40871112
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for edx-braze-client 1.1.4
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.
