vodozemac
Python bindings for vodozemac
Decision gist · record as of 2026-08-14
Yes, if you are building a Matrix client or integration requiring end-to-end encryption and can verify the license terms. The package is actively maintained, has no external runtime dependencies, and offers broad platform support through precompiled wheels. Verify the license declaration in the repository before committing to a production deployment.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; precompiled wheels available for common platforms but source builds may require a Rust toolchain.
- Medium install friction due to compiled wheels across multiple architectures and Python versions.
- Active maintenance with recent release (22 days ago) and ongoing repository activity.
License · maintenance · safety
(unclear) — License status is unclear—no SPDX identifier or raw license text is declared. Verify the actual license terms in the repository before use in proprietary or restricted contexts.
last release 2026-07-23 (22 days) · last repo commit 2026-07-23 · 11 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 75,895 downloads/mo, #14,670 on PyPI
Alternatives
Verify before relying
pip install vodozemac
import vodozemac
# Use vodozemac functions for Matrix encryption operations- What cryptographic operations (key exchange, encryption, decryption, signing) does vodozemac actually expose to Python?
- Is this package intended for end-user applications or primarily for Matrix client library developers?
- What is the actual license governing this package and its Rust source?
What it is and what it does
Vodozemac is a Python binding layer for a Rust cryptographic library designed to support the Matrix protocol's end-to-end encryption. It bridges Python applications to low-level encryption primitives needed for secure communication in Matrix-based systems. The package is distributed as precompiled wheels for multiple architectures and Python versions (3.10 through 3.14), minimizing build complexity on supported platforms.
The library has no runtime dependencies and is maintained actively, with recent updates and a small but established user base. It targets developers building Matrix clients or integrations that require cryptographic operations for encrypted messaging. The unclear license status is a notable consideration for projects with strict licensing requirements.
Use it for
- Building a Matrix client application that needs end-to-end encryption support.
- Integrating encrypted messaging into a Python application using the Matrix protocol.
- Implementing cryptographic key management for Matrix-based communication systems.
- Developing Matrix bots or bridges that must handle encrypted conversations.
- Testing or prototyping Matrix protocol encryption workflows in Python.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are building a Matrix client or integration requiring end-to-end encryption and can verify the license terms.
The package is actively maintained, has no external runtime dependencies, and offers broad platform support through precompiled wheels. Verify the license declaration in the repository before committing to a production deployment.
Install
vodozemac on PyPI
Before you install
Medium install friction due to compiled wheels across multiple architectures and Python versions. Active maintenance with recent release (22 days ago) and ongoing repository activity.
Requires Python 3.10 or later; precompiled wheels available for common platforms but source builds may require a Rust toolchain.
License in practice
License status is unclear—no SPDX identifier or raw license text is declared. Verify the actual license terms in the repository before use in proprietary or restricted contexts.
Quickstart
pip install vodozemac
import vodozemac
# Use vodozemac functions for Matrix encryption operations
Verify before relying
- What cryptographic operations (key exchange, encryption, decryption, signing) does vodozemac actually expose to Python?
- Is this package intended for end-user applications or primarily for Matrix client library developers?
- What is the actual license governing this package and its Rust source?
Package facts
| License | Not declared unclear |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Medium. Platform-specific wheel |
| Runtime dependencies | None |
| Maintenance | Actively maintained 22 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 75,895 / month, #14,670 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Programming Language :: Python :: 3 :: OnlyProgramming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14 |
Evidence: vodozemac-0.10.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl; vodozemac-0.10.0-cp310-cp310-manylinux_2_17_armv7l.manylinux2014_armv7l.whl; vodozemac-0.10.0-cp310-cp310-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl; vodozemac-0.10.0-cp310-cp310-manylinux_2_17_s390x.manylinux2014_s390x.whl; vodozemac-0.10.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl; vodozemac-0.10.0-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.whl; vodozemac-0.10.0-cp310-cp310-musllinux_1_2_aarch64.whl; vodozemac-0.10.0-cp310-cp310-musllinux_1_2_armv7l.whl; vodozemac-0.10.0-cp310-cp310-musllinux_1_2_i686.whl; vodozemac-0.10.0-cp310-cp310-musllinux_1_2_x86_64.whl; vodozemac-0.10.0-cp310-cp310-win_amd64.whl; vodozemac-0.10.0-cp311-cp311-macosx_10_12_x86_64.whl; vodozemac-0.10.0-cp311-cp311-macosx_11_0_arm64.whl; vodozemac-0.10.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl; vodozemac-0.10.0-cp311-cp311-manylinux_2_17_armv7l.manylinux2014_armv7l.whl; vodozemac-0.10.0-cp311-cp311-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl; vodozemac-0.10.0-cp311-cp311-manylinux_2_17_s390x.manylinux2014_s390x.whl; vodozemac-0.10.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl; vodozemac-0.10.0-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.whl; vodozemac-0.10.0-cp311-cp311-musllinux_1_2_aarch64.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “matrix encryption library”
- vodozemacProvides Python bindings for vodozemac, a cryptographic library for…
- matrix-niomatrix-nio is an asyncio-based Python client library for the Matrix…
- mautrixAn asyncio Matrix framework for Python that provides HTTP client…
Give your agent the search over MCP, or paste the wish link into any chat.
More Cryptography packages
Certifi provides Mozilla's curated collection of root SSL certificates for Python applications to validate TLS hosts and verify certificate trustworthiness.
cryptography provides cryptographic recipes and low-level primitives for symmetric encryption, message digests, key derivation, and other common cryptographic algorithms in Python.
Pure-Python RSA encryption, decryption, signing, and key generation following PKCS#1 v1.5, with command-line and library interfaces.
pyOpenSSL wraps OpenSSL's SSL/TLS functionality for Python, providing high-level connection objects and certificate handling through a Python-friendly interface around OpenSSL's cryptographic operations.
Provides Microsoft Entra ID token-based authentication for Azure SDK clients through a set of TokenCredential implementations that handle OAuth flows and managed identity support.
PyNaCl provides Python bindings to libsodium for digital signatures, secret-key and public-key encryption, hashing, message authentication, and password-based key derivation.
See also mautrix · python-olm · matrix-nio · pyDes · pycryptodomex · django-cryptography · django-cryptography-django5 · twofish · pqcrypto