ciris-verify
Python bindings for CIRISVerify hardware-rooted license verification
Decision gist · record as of 2026-08-14
Yes, with conditions. Install if you are building within the CIRIS ecosystem and need to enforce license-based capability gating with hardware-rooted verification. The package is actively maintained, has no known vulnerabilities, and provides clear error handling and testing support. However, the separate binary dependency and AGPL-3.0-or-later license mean you must verify binary availability before deployment and review copyleft obligations for your use case.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- The CIRISVerify binary must be installed separately; the Python package alone is not functional without it.
- Requires Python 3.10 or later.
- Medium install friction: requires the separate CIRISVerify binary to be installed independently of the Python package.
License · maintenance · safety
AGPL-3.0-or-later (agpl) — AGPL-3.0-or-later: derivative works and modifications must be released under the same license. Suitable for open-source projects; proprietary or closed-source applications should review AGPL obligations carefully before adoption.
last release 2026-08-14 (0 days) · last repo commit 2026-08-14 · 2 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 89,780 downloads/mo, #13,636 on PyPI
Alternatives
Verify before relying
pip install ciris-verify
import os
from ciris_verify import CIRISVerify
verifier = CIRISVerify()
status = await verifier.get_license_status(challenge_nonce=os.urandom(32))
if status.allows_licensed_operation():
print(f"Tier: {status.license.tier}")
print(status.mandatory_disclosure.text)- Whether the mandatory disclosure enforcement is a hard requirement or advisory in production deployments.
- Performance characteristics and latency of license verification calls in high-concurrency scenarios.
- Behavior and fallback strategy when the binary is unavailable or verification fails in production.
What it is and what it does
CIRISVerify is a Python wrapper around a hardware-rooted license verification system designed for the CIRIS ecosystem. It lets you check whether a software installation has a valid professional license, what capabilities are available under that license, and whether the system is running in community (unlicensed) mode. The package depends on pydantic for data validation and requires the separate CIRISVerify binary to perform actual verification.
The typical workflow is to initialize a verifier, call get_license_status() with a challenge nonce, and inspect the returned status object to decide whether to enable licensed features or operate in restricted community mode. The package enforces mandatory disclosure: you must display the disclosure text to users to ensure transparency about the agent's capabilities and licensing state. It also provides a MockCIRISVerify class for testing without the binary, and detailed error types (BinaryNotFoundError, BinaryTamperedError, VerificationFailedError) to handle different failure modes.
Use it for
- Gate professional AI agent capabilities behind license verification, falling back to community mode when unlicensed.
- Verify license tier and display appropriate feature sets to users based on their subscription level.
- Detect binary tampering or integrity violations and halt operations immediately as a security safeguard.
- Test license-dependent code paths in CI/CD pipelines using MockCIRISVerify without requiring the binary.
- Handle offline scenarios gracefully using the LICENSED_PROFESSIONAL_GRACE status during grace periods.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, with conditions.
Install if you are building within the CIRIS ecosystem and need to enforce license-based capability gating with hardware-rooted verification. The package is actively maintained, has no known vulnerabilities, and provides clear error handling and testing support. However, the separate binary dependency and AGPL-3.0-or-later license mean you must verify binary availability before deployment and review copyleft obligations for your use case.
Install
ciris-verify on PyPI
Before you install
Medium install friction: requires the separate CIRISVerify binary to be installed independently of the Python package. Active maintenance (released 2026-08-14, last commit 2026-08-14) with current Python support (3.10–3.13). Prebuilt wheels available for macOS, Linux, and Windows.
The CIRISVerify binary must be installed separately; the Python package alone is not functional without it. Requires Python 3.10 or later.
License in practice
AGPL-3.0-or-later: derivative works and modifications must be released under the same license. Suitable for open-source projects; proprietary or closed-source applications should review AGPL obligations carefully before adoption.
Quickstart
pip install ciris-verify
import os
from ciris_verify import CIRISVerify
verifier = CIRISVerify()
status = await verifier.get_license_status(challenge_nonce=os.urandom(32))
if status.allows_licensed_operation():
print(f"Tier: {status.license.tier}")
print(status.mandatory_disclosure.text)Verify before relying
- Whether the mandatory disclosure enforcement is a hard requirement or advisory in production deployments.
- Performance characteristics and latency of license verification calls in high-concurrency scenarios.
- Behavior and fallback strategy when the binary is unavailable or verification fails in production.
Package facts
| License | AGPL-3.0-or-later agpl |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Medium. Platform-specific wheel |
| Runtime dependencies | 1 packagepydantic |
| Maintenance | Actively maintained 0 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 89,780 / month, #13,636 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 4 - BetaIntended Audience :: DevelopersOperating System :: MacOSOperating System :: Microsoft :: WindowsOperating System :: POSIX :: LinuxProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: RustTopic :: Security :: CryptographyTyping :: Typed |
Evidence: ciris_verify-13.2.0-py3-none-macosx_10_12_x86_64.whl; ciris_verify-13.2.0-py3-none-macosx_11_0_arm64.whl; ciris_verify-13.2.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl; ciris_verify-13.2.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl; ciris_verify-13.2.0-py3-none-win_amd64.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 › “hardware license verification”
- ciris-verifyProvides Python bindings to verify hardware-rooted software licenses…
- PyKCS11PyKCS11 provides a Python wrapper around the PKCS#11 cryptographic…
- cocotb-buscocotb-bus provides pre-built testbenching tools and reusable bus…
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 ciris-server · ciris-persist · DafnyRuntimePython · signify · securesystemslib · okta-jwt-verifier · ciris-edge · vonage-verify · service-identity · vonage-verify-legacy