implicant-engine-client
The client half of implicant-engine (import name implicant_engine): the engine contract, the
deployment profile model_profile.json v4, the frozen IMPLCTX envelope codec, the on-disk key
store, the engine registry, and the float quantization of the input pool.
This is everything the SDK needs to run an FHE inference on the client side, and nothing else: no
model reader, no evaluation in the clear, no reference engine, no harness (decision E-13). Those
live in implicant-engine-server.
See the repository README.md and docs/architecture.md.
1 maintainer
Metadata
1 maintainer
Release files for implicant-engine-client 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| implicant_engine_client-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / implicant_engine_client-0.1.1-py3-none-any.whl
| Download URL | implicant_engine_client-0.1.1-py3-none-any.whl |
|---|---|
| Size | 26.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ae0c35c494937b551176e44def9900941fc3188fdf673ba079a4addbfa55ef78
|
|
BLAKE2b-256 checksum How to use checksums |
4d5047f2d53e200e3b9b5e41d782e4ca45367132cca139183cb295cd8c11e3ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 2, 2026.
Transparency logSecurity for implicant-engine-client 0.1.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 1 file in this release has been uploaded with provenance metadata.
Attestation for implicant_engine_client-0.1.1-py3-none-any.whl
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 Oct 2, 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.
