Eqty Python SDK
Create signed, verifiable provenance for data, models, prompts, code, and Python computations.
The SDK records inputs, outputs, and execution relationships as an Integrity Manifest that you can inspect in Eqty Explorer.
Install
Python 3.10 or newer is required.
python -m pip install eqty_sdk
Create your first manifest
This example registers an input dataset, records a computation, and exports the resulting manifest.
from pathlib import Path
from eqty_sdk import Dataset, SIGNER_ALGORITHMS, Signer, compute, init, set_active_signer
# Initialize local SDK storage and the signer used for generated statements.
context = init().set_store_all_blobs(True).get_default_context()
set_active_signer(Signer.new(SIGNER_ALGORITHMS.SECP256R1))
input_data = Dataset.from_object({"customer_id": 42, "status": "active"})
@compute(metadata={"name": "Normalize customer status"})
def normalize(dataset: Dataset) -> Dataset:
return Dataset.from_object({"customer_id": 42, "status": dataset.value["status"].upper()})
normalize(input_data)
context.export(Path("manifest.json"))
Import manifest.json into Eqty Explorer to inspect the assets, computation, and signed statements.
Learn more
For contributing to the SDK itself, see the repository's developer README.
Metadata
Release files for eqty-sdk 2.5.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 | Actions |
|---|---|---|---|---|
| eqty_sdk-2.5.1.tar.gz | 506.1 kB | With provenance | Details for eqty_sdk-2.5.1.tar.gz |
Built distributions (wheels)
Total release size: 110.1 MB
Release files / eqty_sdk-2.5.1.tar.gz
| Download URL | eqty_sdk-2.5.1.tar.gz |
|---|---|
| Size | 506.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe1305e5b403969b95a2402e2a1cf09ea7c959d05975abf1c54156d674785cbe
|
|
BLAKE2b-256 checksum How to use checksums |
9d5941987bbf6e690c7ed358157a4b91a42f0d9ed9b1592a306398b1b130b9f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / eqty_sdk-2.5.1-cp38-abi3-win_amd64.whl
| Download URL | eqty_sdk-2.5.1-cp38-abi3-win_amd64.whl |
|---|---|
| Size | 12.9 MB |
| Tags | CPython 3.8 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
d808cb6da65b726b66c6e69ac730a42afe9fca3d27a0feb93e7e3349eb52f444
|
|
BLAKE2b-256 checksum How to use checksums |
bd28e0ebaff67938e31e28f6a8a8b06926f6474fd1a46340041f683d6ffce716
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / eqty_sdk-2.5.1-cp38-abi3-musllinux_1_2_x86_64.whl
| Download URL | eqty_sdk-2.5.1-cp38-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 17.7 MB |
| Tags | CPython 3.8 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
ac86c00dc14a567c82ff70117030c2362659779a6cc5af5fa0e6cc679454662b
|
|
BLAKE2b-256 checksum How to use checksums |
e774819b0e5e0c0add9eb81be54cb4e1c51fb0a55696244425a8b866e2b9b32f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / eqty_sdk-2.5.1-cp38-abi3-musllinux_1_2_aarch64.whl
| Download URL | eqty_sdk-2.5.1-cp38-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 17.4 MB |
| Tags | CPython 3.8 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
6c026eb7a4cb5490944bc28900b48c0b606efa6489775ec5341d08fba2fef1b1
|
|
BLAKE2b-256 checksum How to use checksums |
9b753040bea5e7d34335688484a55779db2b36e6c97c93e2b0b60208886502b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / eqty_sdk-2.5.1-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | eqty_sdk-2.5.1-cp38-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 17.3 MB |
| Tags | CPython 3.8 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
c69080327aace06dfd1d486ccdc993c65bfc0168ca078ddeddb58ceeef00ad47
|
|
BLAKE2b-256 checksum How to use checksums |
17eaa9aa30a6c0744a39de3836929c51e455a98f38ea35f782217aaf3c4b4e97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / eqty_sdk-2.5.1-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | eqty_sdk-2.5.1-cp38-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 16.8 MB |
| Tags | CPython 3.8 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
11f1f5ce9c767af94c47ff161fc860fae017b261905ffb51768957bed2488b81
|
|
BLAKE2b-256 checksum How to use checksums |
e8b888f075fe78dcc9de4dcaec8f7b4933439c82f5dde8ec923af5229fa8cf00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / eqty_sdk-2.5.1-cp38-abi3-macosx_11_0_arm64.whl
| Download URL | eqty_sdk-2.5.1-cp38-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 13.5 MB |
| Tags | CPython 3.8 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
01fad750bac666c1d9587aa9cd2bab4b9ba9d596142e30c2ee7f17ace439fa7f
|
|
BLAKE2b-256 checksum How to use checksums |
2e71a8010e027bc504e6e9d9fa310d62e39733ed793ad6c9ba85e9c60871ea75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / eqty_sdk-2.5.1-cp38-abi3-macosx_10_12_x86_64.whl
| Download URL | eqty_sdk-2.5.1-cp38-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 14.0 MB |
| Tags | CPython 3.8 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
dfb86fc2a351a4a619918d2767a016e252d6a572936d9632731f1d7aac4b9984
|
|
BLAKE2b-256 checksum How to use checksums |
ea47e1055c776ff7b5e15c49b4f96c40b49e81e8e61d0a76d507c5f499d765fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logSecurity for eqty-sdk 2.5.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.
Full provenance
All 8 files in this release have been uploaded with provenance metadata.
Attestation for eqty_sdk-2.5.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
