clifft-qiskit
A Qiskit BackendV2 provider for the
Clifft near-Clifford simulator.
Run Qiskit circuits on Clifft without hand-writing Stim.
Install
pip install clifft-qiskit
Quickstart
from qiskit import QuantumCircuit
from clifft_qiskit import ClifftProvider
qc = QuantumCircuit(2, 2)
qc.h(0); qc.cx(0, 1); qc.measure([0, 1], [0, 1])
backend = ClifftProvider().get_backend("clifft")
counts = backend.run(qc, shots=1000).result().get_counts()
print(counts)
Supported basis
Clifford+T plus single-qubit rotations: h s sdg x y z cx cy cz t tdg rx ry rz
(+ measure). Higher-level gates (ccx, u, controlled rotations, …) are
decomposed into this basis by qiskit.transpile inside run().
Limitations
- Terminal measurement + counts only (no mid-circuit measurement / feedforward).
resetand other non-unitary ops raiseQiskitError.- Single synchronous backend, all-to-all connectivity.
License
Apache-2.0.
1 maintainer
Metadata
1 maintainer
Release files for clifft-qiskit 0.1.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 | Actions |
|---|---|---|---|---|
| clifft_qiskit-0.1.0.tar.gz | 56.6 kB | With provenance | Details for clifft_qiskit-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| clifft_qiskit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for clifft_qiskit-0.1.0-py3-none-any.whl |
Total release size: 66.2 kB
Release files / clifft_qiskit-0.1.0.tar.gz
| Download URL | clifft_qiskit-0.1.0.tar.gz |
|---|---|
| Size | 56.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c261c1af28f6f67028ca16447bff3a33b031f3182942bc418246faa8da7aaf00
|
|
BLAKE2b-256 checksum How to use checksums |
50358fd744f7779a1ae509809f81b872a4d42f337cdb25d6c5e880284aeb6212
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 6, 2026.
Transparency logRelease files / clifft_qiskit-0.1.0-py3-none-any.whl
| Download URL | clifft_qiskit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e76f67c86fa253ddda9d50fab972525ceb1f3ceaa5e7bd48140851094476ab8
|
|
BLAKE2b-256 checksum How to use checksums |
d13379654eebf084e6f5011dbf19ad7e5efe319e8439b4373fa1419e5f0a3f47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 6, 2026.
Transparency logSecurity for clifft-qiskit 0.1.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 2 files in this release have been uploaded with provenance metadata.
Attestation for clifft_qiskit-0.1.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 Jul 6, 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.
