Microsoft SEAL For Python
This is a python binding for the Microsoft SEAL library.
Microsoft SEAL is an easy-to-use open-source (MIT licensed) homomorphic encryption library developed by the Cryptography Research group at Microsoft.
pybind11 is a lightweight header-only library that exposes C++ types in Python and vice versa, mainly to create Python bindings of existing C++ code.
Contents
Install
SEAL-Python is available on PyPI:
python -m pip install seal-python
Build
On macOS, use the same deployment target for both the SEAL static library and the Python extension to avoid linker warnings about mismatched macOS versions:
export MACOSX_DEPLOYMENT_TARGET=$(python3 - <<'PY'
import sysconfig
print(sysconfig.get_config_var("MACOSX_DEPLOYMENT_TARGET") or "15.0")
PY
)
-
Linux
Recommend: Clang++ (>= 10.0) or GNU G++ (>= 9.4), CMake (>= 3.16)
# Optional sudo apt-get install git build-essential cmake python3 python3-dev python3-pip # Get the repository or download from the releases git clone https://github.com/Huelse/SEAL-Python.git cd SEAL-Python # Install dependencies pip3 install numpy pybind11 # Pull the SEAL git submodule update --init --recursive # Get the newest repositories (dev only) # git submodule update --remote # Build the SEAL lib without the msgsl zlib and zstandard compression cd SEAL cmake -S . -B build -DSEAL_USE_MSGSL=OFF -DSEAL_USE_ZLIB=OFF -DSEAL_USE_ZSTD=OFF # macOS: cmake -S . -B build -DSEAL_USE_MSGSL=OFF -DSEAL_USE_ZLIB=OFF -DSEAL_USE_ZSTD=OFF -DCMAKE_OSX_DEPLOYMENT_TARGET=${MACOSX_DEPLOYMENT_TARGET} cmake --build build cd .. # Run the setup.py, the dynamic library will be generated in the current directory python3 setup.py build_ext -i # Test cp seal.*.so examples cd examples python3 4_bgv_basics.py
Build examples:
-DSEAL_BUILD_EXAMPLES=ON -
Windows
Visual Studio 2019 or newer is required. x64 support only! And use the x64 Native Tools Command Prompt for VS command prompt to configure and build the Microsoft SEAL library. It's usually can be found in your Start Menu.
# Run in "x64 Native Tools Command Prompt for VS" command prompt cmake -S . -B build -G Ninja -DSEAL_USE_MSGSL=OFF -DSEAL_USE_ZLIB=OFF -DSEAL_USE_ZSTD=OFF cmake --build build --config Release # Build pip install numpy pybind11 python setup.py build_ext -i # Test cp seal.*.pyd examples cd examples python 4_bgv_basics.py
Microsoft SEAL official docs.
-
Docker
requires: Docker
To build source code into a docker image (from this directory):
docker build -t huelse/seal -f Dockerfile .
To use the image by running it as an interactive container:
docker run -it huelse/seal
Note
-
Serialize
See more in
examples/7_serialization.py, here is a simple example:cipher.save('cipher') load_cipher = Ciphertext() load_cipher.load(context, 'cipher') # work if the context is valid.
Supported classes:
EncryptionParameters, Ciphertext, Plaintext, SecretKey, PublicKey, RelinKeys, GaloisKeys -
Other
The latest SEAL library includes many changes. We’ve tried to make the Python API easier to use, but some issues may still exist. If you encounter any problems or bugs, please report them on issues.
FAQ
-
ImportError: undefined symbol
Build a shared SEAL library
cmake . -DBUILD_SHARED_LIBS=ON, and get thelibseal.so,then change the path in
setup.py, and rebuild. -
ImportError: libseal.so... cannot find
a.
sudo ln -s /path/to/libseal.so /usr/libb. add
/usr/local/libor theSEAL/native/libto/etc/ld.so.confand refresh itsudo ldconfigc. build in cmake.
-
BuildError:
-
C++17 at least
-
x86_64 is required, which
x86_32is not supported
-
-
ModuleNotFoundError: No module named 'seal'
The
.soor.pydfile must be in the current directory, or you haveinstallit already. -
Windows Error LNK2001, RuntimeLibrary and MT_StaticRelease mismatch
Only
x64is supported, Choosex64 Native Tools Command Prompt for VS. -
Warning about building the dynamic library with static library in MacOS, etc.
-
Build a shared SEAL library by adding a CMake option
-DBUILD_SHARED_LIBS=ON -
Edit
extra_objectsin setup.py to*.dylibor else.
-
Typing
This project now ships seal.pyi and py.typed for Python type checking (PEP 561).
After build/install, editors such as Pylance/Pyright/mypy can use these hints for autocomplete and static analysis.
Release
Use RELEASE.md for the full PyPI release checklist.
Quick commands:
python3 setup.py sdist bdist_wheel
python3 -m twine check dist/*
python3 -m twine upload dist/*
Contributing
-
Professor: Dr. Chen
Metadata
Release files for seal-python 4.4.0
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 | |
|---|---|---|---|---|
| seal_python-4.4.0.tar.gz | 23.5 kB | With provenance | Details |
Built distributions (wheels)
Total release size: 12.7 MB
Release files / seal_python-4.4.0.tar.gz
| Download URL | seal_python-4.4.0.tar.gz |
|---|---|
| Size | 23.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b16b21796f1f6b236a0974f15d95822335d6c85feed029a564e57f538f2db282
|
|
BLAKE2b-256 checksum How to use checksums |
05b9a48aa592534265f23939698c4d0f890c786cf9b39c4780c83507cf431172
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp314-cp314-win_amd64.whl
| Download URL | seal_python-4.4.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 478.9 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c23897f30dc3e8c2e70263548c6588d12445bc429b080ac39671d8ea097ed3a9
|
|
BLAKE2b-256 checksum How to use checksums |
a5bdcfde150ea70cbab54855eb4d8444f49c81d3b5a88085be1a6308fad8f642
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | seal_python-4.4.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 780.6 kB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
1dbee5f65b99e5d890b618f7f0b169f3d5e365f8e31793ee5ae2aa603c4f4318
|
|
BLAKE2b-256 checksum How to use checksums |
91286d954de722397ceca9bef8b32029f2330f03fc14f35eba88074554889270
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | seal_python-4.4.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 670.2 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f2103dc8d97f4adc78d05aea4726b6f60e5e661c4d887af810a04505f58d6a63
|
|
BLAKE2b-256 checksum How to use checksums |
be3123c10c4e620cb9240fb60ad80ba9b984b4edc65977645496c6cce3821a0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp313-cp313-win_amd64.whl
| Download URL | seal_python-4.4.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 465.6 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7fa600b36bb00216c896b9a0159eef5c573b6e2960a2a2b6383c9cfe934016ab
|
|
BLAKE2b-256 checksum How to use checksums |
15bde32e6df4c86989ee31291521b4e53019bc33563865af8802810c825a6138
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | seal_python-4.4.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 780.0 kB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
38940827d6a28149a0e0f42917e2ddabb317cf68e1fa2cb5a33a3624de35650d
|
|
BLAKE2b-256 checksum How to use checksums |
69db217c8dc6cacc0ed6a30d0213c9e9f5204139f2441a77813895b2eeb8e1a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | seal_python-4.4.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 669.3 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6ea85dfe5e825d86e161987526d41841ee528458dd1e64665769b2606eee5f1a
|
|
BLAKE2b-256 checksum How to use checksums |
ffe12a7a00abec8f9d7b34890d0233738b353dd62cd31d98a55be242e3d97058
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp312-cp312-win_amd64.whl
| Download URL | seal_python-4.4.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 465.9 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7ad5a477be2d3dc6a8b2ad300c4e4662d3f3a37d81bc721389cfc94e3badef86
|
|
BLAKE2b-256 checksum How to use checksums |
30b47d414ef79e95a3374496ce9c3d4150bc5bb0e22f61e649cd0ce0639be086
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | seal_python-4.4.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 780.3 kB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
83fc29bec0533e1bbd5d29e10faa60642378c767e1a17d8562a7e611be8d5399
|
|
BLAKE2b-256 checksum How to use checksums |
888b1418a6c6f8ab61a198c932f92c1bc8f4e801e42cca0fe064d78425d157e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | seal_python-4.4.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 641.8 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1c262095f1c586d2418e8f462bbdeac0d8725a77afce76f72344ce6699484cb8
|
|
BLAKE2b-256 checksum How to use checksums |
daa470342d6cca0c69cf6dcf87606d318165392fb1ddce14b57649c85bd7d2b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp311-cp311-win_amd64.whl
| Download URL | seal_python-4.4.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 462.2 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fcaec18d87b3019955901480156c9bba6eed08b0f786a0da23c9a8a7e2c1718b
|
|
BLAKE2b-256 checksum How to use checksums |
060b2ca058c1b8829c0e06de0ee837e769bfd7fb750bcb140afcf5cba656acf5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | seal_python-4.4.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 777.4 kB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
3722ee02cd18afd562b6b8623c14e3153e8b6dd3c23f260ef94ba88a5c02f42e
|
|
BLAKE2b-256 checksum How to use checksums |
a6e21e185ea91c0df665551318f2399f06acd72b92cd38a9541be399fe486f22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | seal_python-4.4.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 665.9 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8b43d6c43d0a87e22b5810ddc88538d07f90d1c2f33522c779f10495872d7aeb
|
|
BLAKE2b-256 checksum How to use checksums |
be8aecb19b21012b3957f3aae8cfcf7bb7dd2a84bfd7588c37dc0cb0f18ce85b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp310-cp310-win_amd64.whl
| Download URL | seal_python-4.4.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 460.9 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
04eac0e8a87e1e82e1550b78d564f7b1f2584b592c967a506aee19c68e8cdb9d
|
|
BLAKE2b-256 checksum How to use checksums |
d7d3372f98cb1f5fb5e885714e667c31a15c40510f82869b2cc30717922062b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | seal_python-4.4.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 775.2 kB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
025e09f4e437015ea148038f0bc237ce6bc4ec0314ad6d0363b119c50120f4d2
|
|
BLAKE2b-256 checksum How to use checksums |
f9af741bf6e91493f0727e7b113e7e3155673e1871685c96d8c18bf67ebb1907
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | seal_python-4.4.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 638.1 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b90327901117cd961e69ce9967be93fccbeca50e8ada113ff697a51b9feeedc8
|
|
BLAKE2b-256 checksum How to use checksums |
67c3dbd96d8d3237047212277f84035d129cbe6f87912318d54d553b527fb5cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp39-cp39-win_amd64.whl
| Download URL | seal_python-4.4.0-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 461.0 kB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
4c49b71580fb65a205a93f7802e00d6c253e29bae67ed18c1aa892aad1c20246
|
|
BLAKE2b-256 checksum How to use checksums |
3a3e2ec94fe07b5962a36dd8861171e89e4474952f312328d74b8f6bc6c851cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | seal_python-4.4.0-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 775.9 kB |
| Tags | CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
607e3bea24bb746bc069455a2ae57ddefb5c0cc8114c9cefb5b124b60fb681ff
|
|
BLAKE2b-256 checksum How to use checksums |
a03068b95b8f30da4e458339b2089af0888481e7ae92fcce3c5fd63a76f1a908
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | seal_python-4.4.0-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 665.0 kB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0a4ef82f1c0cea56da50eb13f290253fa048501f16674b8683dec8da0453b468
|
|
BLAKE2b-256 checksum How to use checksums |
06c68fd064b3980b311e1a2ba0bbd0c497808222718432a76d0472bcb25f5b33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp38-cp38-win_amd64.whl
| Download URL | seal_python-4.4.0-cp38-cp38-win_amd64.whl |
|---|---|
| Size | 461.6 kB |
| Tags | CPython 3.8 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
88bded46ab6e3e95ab91dd70193db999c3ca922d66a51fe82a4620af51823d95
|
|
BLAKE2b-256 checksum How to use checksums |
1a159b0b7405517b460e7e3277b439d9578d54b5ae70ad22a23df26c2cac3b15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logRelease files / seal_python-4.4.0-cp38-cp38-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | seal_python-4.4.0-cp38-cp38-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 775.0 kB |
| Tags | CPython 3.8 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
eb122f2084d3568a3b67290e2826f6d19308f032d2319b785497c7391c40c846
|
|
BLAKE2b-256 checksum How to use checksums |
a3d35da4627a57dd9fdf42507538f4c04ac58c7fc03a0804fff776857b53631a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 3, 2026.
Transparency logSecurity for seal-python 4.4.0
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 21 files in this release have been uploaded with provenance metadata.
Attestation for seal_python-4.4.0.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 Aug 3, 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.